Thank you for all your feedback and voting on this feature.
We recently had a Product Roadmap update, and there has now been an item added to the Roadmap :
EDIT: The target date of release supporting Multiple Custom Domains per tenant has been changed, currently the estimated time is set to Q4 2025 (OCT-DEC).
Support Multiple Custom Domains per tenant - Target release in Q3 2024 (Aug-Oct). (Please note that the target dates may be subject to change). We do not have any further details at this time.
Although the release date is quite far out, it is great to see that our product team has added this feature to the future plans. Thanks again for all the feedback that helped get this feature on the roadmap.
EDIT: The target date of release supporting Multiple Custom Domains per tenant has been changed, currently the estimated time is set to Q4 2025 (OCT-DEC).
The current description mentions about the ability to create more than one customized login experience within a single tenant which can be catered towards different applications or Organizations. Although currently no mention for branding by each custom domain. We may have more details in the future or you can look to raise an additional feedback post for this specific use case, thanks!
Hi all! My name is Carolyn, and Iām the research ops specialist for the Auth0 research team. We are recruiting for a study that requires your feedback on how your company handles and manages branding needs to provide multiple login experiences.
Weāre conducting 45-minute interviews. These sessions will be conducted via our user research platform Great Question , and they will be recorded for internal purposes only. As a token of appreciation for your time and feedback, weāre offering a $60 incentive.
If youāre interested, please complete the screener to see if you are eligible to participate here. Feel free to follow up with me if you have any questions!
Hi Oleh! My name is Carolyn, and Iām the research ops specialist for the Auth0 research team. We are recruiting for a study that requires your feedback on how your company handles and manages branding needs to provide multiple login experiences. My team thinks you would be a great candidate for the study.
Weāre conducting 45-minute interviews with a $60 incentive through our tool GreatQuestion. If youāre interested, please complete the screener to see if you are eligible to participate here. We will reach out to you within 48 hours to schedule an interview. Feel free to follow up with me if you have any questions!
Hi Vaclav! My name is Carolyn, and Iām the research ops specialist for the Auth0 research team. We are recruiting for a study that requires your feedback on how your company handles and manages branding needs to provide multiple login experiences. My team thinks you would be a great candidate for the study.
Weāre conducting 45-minute interviews with a $60 incentive through our tool GreatQuestion. If youāre interested, please complete the screener to see if you are eligible to participate here. We will reach out to you within 48 hours to schedule an interview. Feel free to follow up with me if you have any questions!
Hello everyone, Iāve been trying to address this issue through direct channels with Auth0. While Sales has been unresponsive, the development team provided some solutions. The product team has this feature in the backlog, but details are limited. To expedite, we need more visibility. Please upvote the ticket and reach out to sales for support. Thank you.
Just came to vote on this as it would be extremely helpful to allow us to change the custom domain with a staged approach without breaking all of our customerās SSO connections that use our custom domain in their callback URL. As an enterprise customer, the timeframe update is very disappointing.
This is incredibly important if you need to change your domain name as well. You will otherwise lock users out. Any customers of yours with SSO configured will need to update their configuration and so on. It may not be so easy to update mobile apps where now someone is using an older version that has an old custom domain configuration. Links for email verification, password reset, etc. they all break.
Like others have said this isnāt just a convenience, this is a mandatory feature. In the very least a way to migrate from one to another so you donāt have service interruption. There are simply times when a domain must change (legal reasons, etc.) and to have a service interruption here, youāre honestly breaking your SLA. Not really sure what the mandatory support charges are that came into effect either, but boy what are we getting for that?
Very unfortunate to see this slated for Q4 2025 after all this time.
thank you for giving this topic some attention. I donāt have access to the former account. So I didnāt get a notification. At the moment it is out of scope for me since. I am not working with Auth0 anymore
I had same experience when I was trying to solve this problem. The dev team is trying their best, but sales simply has different priorities. As usually
Fortunately I donāt have to work on the project which had this problem anymore. I learned my lesson with Auth0. The way their business prioritise roadmap push me look for another solutions for both B2B and B2C. My personal suggestion would be chose different solution for B2B if you need multiple domains. Waiting for major feature request like this 5 years is simply too much
Auth0 is robust and secure, but for B2C or big scaling it is not best solution. It is way too expensive and way to limiting
Upvoting this, I am surprised this has not been supported in so long. We have multiple SSO integrations with our customers where they have already configured a redirect URI in their configurations. We would like to add another domain for newer integrations and not require the older ones to update their redirect URIs. This seems like a typical migration scenario for a domain that is completely unsupported.
Still waiting for this feature. Many customers in our multi-tenant Auth0 Tenant want to use embedded login in regular web apps with email/password. In order for this to work well, we understand that we must eliminate the CORS issues by putting each customerās domain in front of the Auth0 Authorization Server. We do our best to direct them all towards universal login, but we get a lot of friction about having redirects in signup form workflows, understandably.
:
and wanted to reiterate that the timelines for feature requests are subject to potential changes.