The end-of-life date for skipping session reuse (SSO) after prompting users for their organization name was May 1, 2026. The process to transition tenants out of the deprecated behavior has the following phases:

• May 4, 2026 - Tenants tagged as development or staging tenants. The transition occurs according to the tenant's environment tag when changes roll out for each environment. Therefore, changing a development tenant to production after the rollout phase is complete will not reinstate the deprecated behavior.

• TBD - Outstanding tenants, including production tenants.

The dates indicate when each phase begins. The rollout of each phase may take several weeks, so tenants within a phase may experience the change at different times. Updates will be posted in this article as the transition timeline is finalized.

What is the impact of the change?

Once a tenant transitions to the new behavior, Auth0 will reuse applicable authenticated sessions after the user enters their organization name. Already signed-in users will no longer be forced to log in again solely because of the login flow, including the organization name prompt.

Consequently, since users from connections to external identity providers do not re-authenticate, their profile attributes will not refresh, as Auth0 reuses a previous session rather than forcing a new login via the external identity provider.

• End of Life (EOL)
• Organizations
• Prompt for Organization Name

Auth0 updated the behavior for login requests that prompt users for the organization name as part of a calendar-year 2026 change designed to improve user experience.

On October 31, 2025, Auth0 announced changes to how the service handles login flows that prompt for the organization name. The information provided in the original announcement is available in the respective Dashboard and Support Center notification.

For applications that require users to log in again after being prompted for the organization name, update them to use alternative methods that achieve a similar experience. For example, OIDC applications can explicitly request re-authentication.