Enabling Custom Domain with Enterprise connections

This article explains how to address an issue where migrating to a custom domain for authentication requires updating redirect URLs for numerous Enterprise Connectors. When organizations have a large number of OpenID Connect (OIDC) connectors from customers, coordinating updates to the valid redirect URL on the customer Identity Provider (IdP) side may not be feasible. This guide provides a workaround to ensure a seamless transition without service interruptions.

• Custom Domains 

• Enterprise Connections 

• OpenID Connect (OIDC) 

• Identity Providers (IdP)

To avoid immediate coordination with all customers to update their OIDC applications, implement the following workaround: 

1. Ask customers to add the new redirect URL containing the custom domain to their existing IdP configuration.

2. Ensure the original redirect URL using the standard Auth0 domain remains active on the IdP.

3. Verify that all IdPs are configured with both the standard and custom domain redirect URLs.

4. Switch the login flow to the custom domain once all configurations are verified.

    

This approach allows for a transition to the custom domain without downtime or the need for simultaneous updates across all connectors.

NOTE: This workaround relies on the ability of the IdP to support multiple callback configurations, as discussed in Multiple callback URLs for a single OAuth 2.0 app.