Configure Single Sign On for Auth0 Dashboard: Migrate Tenant Members

Overview

Enterprise customers can configure Auth0 to allow Tenant Members to use an Enterprise identity provider(IdP) to authenticate to the Auth0 Dashboard through Single Sign-On (SSO). Creating an SSO integration adds an alternative login method, requiring administrators to re-invite Tenant Members with their new SSO identities to the tenants. Administrators migrate Tenant Members before or after enabling Home Realm Discovery (HRD), or by using Auth0 Teams when Tenant Member Management is enabled.

Applies To

  • Auth0
  • Single Sign-On (SSO)
  • Auth0 Dashboard
  • Tenant Members

Cause

Creating an SSO integration with an enterprise identity provider will add an alternative login method for members. By default, users can authenticate to the Public Cloud Dashboard using any available social identities (LinkedIn, Microsoft Account, GitHub, or Google) or create their own email/password identity. Since every authentication method constitutes different identities and, consequently, different Dashboard users, the SSO identities are yet another user identity that needs to be invited to every tenant to access the Manage Dashboard for them. 


The migration process essentially consists of re-inviting the tenant members with their new SSO identities to the tenants.

Solution

How do administrators migrate Tenant Members before turning on Home Realm Discovery?

Before administrators enable Home Realm Discovery (HRD), they must create a new invitation URL, and the recipient must authenticate via a dedicated SSO login URL to establish the new identity and accept the invitation.

  1. Create a new invitation URL.
  2. Sign in with the new authentication method using the URL provided by support, like below, preferably from an incognito window or a browser different from the usual.
  3. Complete the profiling step if this is the first time authenticating with the new method to view the Auth0 user onboarding screen.
    Auth0 User Onboarding
  4. View the Unable to create a Team or a Tenant message on the dashboard.
    Unable to create a Team or a Tenant 
  5. Paste the invitation URL from the email into the same browser where the recipient authenticated with the new SSO identity.
  6. Confirm the invitation to make the new identity an administrator of the tenant.

 

How do administrators migrate Tenant Members after turning on Home Realm Discovery?

Once Home Realm Discovery (HRD) is enabled, users can be redirected automatically to their enterprise identity provider when they enter an email address associated with the configured domain. To migrate existing tenant members, follow these steps:

  1. Log in with an identity that is already an administrator of the tenant. If this is an email/password identity that has the email domain already associated with HRD, use the following URL to force an authentication with email/password:
    https://manage.auth0.com/login?connection=auth0
  2. Create an invitation for the new member.
  3. Sign out of the Auth0 Dashboard if previously logged in with an old identity.
  4. Select the invite URL to sign in again.
  5. Enter the email address of an associated domain to see the password field disappear, and select the login button to redirect to the enterprise IdP.

 

How do administrators handle migration when Auth0 Teams has Tenant Member Management enabled?

When Auth0 Teams has Tenant Member Management enabled in the Team Dashboard, a Team Owner must invite the users as Team Members and assign them to the tenants.

  1. Invite the users as Team Members by following the Invite a New Team Member documentation.
  2. Assign the users to the tenants from the Team Dashboard after the user accepts the invite with the new SSO identity by following the Assign Team Member to Tenants with Tenant Member Management documentation.

 

Private Cloud Dashboard SSO Connections

For Private Cloud SSO connections, Auth0 Support must provide the appropriate URLs for triggering SSO authentication and bypassing HRD because these URLs are specific to each private instance.

 

Related References

Recommended content

No recommended content found...