We are planning to use branding and have our app hosting on the Domain atxxx.dev.company.com
Navigating to the page we see the login page and able to see the email customised templates working.
Now we want to keep the same domain for our app as well, basically saying atxxx.dev.company.com/home
to navigate to our site with the tokens after sucessfull login. Is this the correct way of using the branding , is this flow possible or would it result in 429 ? What could be the possible approach if we want to keep the same domain for both Login and the App while also using the branding ?
You may need to write out some custom code to ensure your widget handled the same domain limitation- you can use our Embedded widget to do just that - see deployment models.
Do you have a custom server, a reverse proxy or any other way tho
There are multiple ways to do this - basically - you can create subdomains for specific app branding experience and point it to redirect to your application hosted in the /home route.
Redirect model
Use one subdomain for authentication: login.dev.company.com (pointing to the IdP).
Use another subdomain for the application: app.dev.company.com (pointing to the App’s infrastructure).
Configure the IdP to redirect back to app.dev.company.com/home (or wherever the app handles the post-login redirect) after successful authentication.
Embedded - Avoids redirect and authenticates on the same domain -