We have a customer who wants have their own custom domain to access our saas product. We use auth0 in our product. After configuring the domain for the customer. what changes do I need to make for auth0 to handle seamless user login and sso login.
Hi @ankit5
Welcome to the Auth0 Community!
After you have configured a custom domain on your tenant ( more details on this doc ), the only changes that you would want to make in order to use the custom domain is change it within your applications as well, in order for them to use it instead of your canonical, Auth0 domain. This has been mentioned on our doc right here as well.
Another resource that covers some common questions that I recommend looking through is this Knowledge Article, albeit it is a little old.
Let me know if you have other questions.
Have a great one!
Gerald
Hi @gerald.czifra,
Please find our complete use case here:
Task:
- login page should be customized for the customer using our app (my.app)
- users login with their social credentials
- redirect to their own custom domain (c1 .com) pointing to our app (my.app)
- Users must be able to login with our own login page but still get redirected to (c1 .com)
Constraints and questions:
- Use only one tenant
- Can the members login from the regular (my.app) login page ?
- where is the member data stored when they login with the organization login page ?
- After login, can we redirect to their custom domain (c1. com) accessing our app (my.app). if yes how do we configure it ?
- How do we achieve the above features programmatically ?
Thanks for getting back to me.
By “custom domain,” I mean allowing users to access our app (e.g., my.app.com) using their own root domain (e.g., customer.product.com).
In this scenario, what changes are required to ensure seamless user login? Additionally, what steps should I take to properly handle SSO?
Looking forward to your insights!