New Universal Login Experience

Auth0's New Universal Login Experience provides a reimagined login flow, with a fresh UX design and lightweight pages. When you pick this new experience, Auth0 will use it for all pages that haven't been customized. You can enable it from the Universal Login Settings dashboard section.

The key structural difference from the Classic Experience is that the former uses Javascript widgets in all the pages, while the New Experience is rendered on the server and does not require Javascript.

From a functional perspective, the New Experience has much better support for Localization, a better MFA experience, and several improvements across all pages. The New Experience is being actively developed, so new features are regularly added. However, there is still a feature gap with the Classic Experience, and some pages in the New Experience have certain differences detailed below.

You can specify a Liquid Template for all pages in the login flow with Page Templates.
You can configure the favicon URL and a custom logo URL by using the Universal Login configuration page or the Branding API.
You can override any text by using the Text Customization API.

If you are using Development Keys for Social Providers:
- Single Sign-on (SSO) and Silent Authentication will work properly, which does not happen in the Classic Experience.
- Users will see a warning in the login page mentioning that the tenant is configured with Development Keys.
A button will be rendered for each social and enterprise connection.
If you redirect users to the /login page directly, they will get an error unless they have configured the default login route. You should always redirect users to the proper authorization request endpoint (e.g., /authorize if you are using OpenID Connect).
You can specify the login_hint when redirecting to Auth0, and it will be used to populate the username/email field for the login or signup page.

You can make users land directly on the Signup page instead of the Login page by specifying the screen_hint=signup parameter when redirecting to /authorize. Note that this can be combined with prompt=login, which indicates whether you want to always show the authentication page or you want to skip if there's an existing session.

`/authorize` parameters	No existing session	Existing session
no extra parameters	Shows the login page	Redirects to the callback url
`screen_hint=signup`	Shows the signup page	Redirects to the callback url
`prompt=login`	Shows the login page	Shows the login page
`prompt=login&screen_hint=signup`	Shows the signup page	Shows the signup page

If users have more than one multi-factor authentication (MFA) factor enrolled (e.g., SMS and Push notifications), the new MFA page will let the user select which one they want to use.
You can use Voice or Email as an MFA factor
If you are using the Guardian SDK to create your own native application to handle Push Notifications, you can configure the name of the application and the URLs to download them in the Push via Auth0 Guardian option in the MFA Dashboard > MFA section.
If you have a rule that sets the MFA provider to google-authenticator you need to enable the OTP factor in the Dashboard > MFA section.

In the Classic Experience, you can configure a url to redirect users after completing the password reset. The URL will receive a success indicator and a message. The New Experience will redirect the users to the default login route when it succeeds and will handle the error cases as part of the Universal Login flow. The Redirect URL in the email template will be ignored.

Please note that you must provide an Application Login URI under Application Settings for the redirect URLs to work.

If the Database Connection is set to Require Username, the password reset flow will ask the user for the username and send a password reset email to the associated email address.

When using Custom DB Connections:

The password reset flow will function properly even if you return errors from the change password script.
The errors returned in ValidationErrors or WrongUsernameOrPasswordError will be displayed in the corresponding pages.

After a user clicks the email verification link, they'll be redirected to a page that will confirm that their email is verified. If the default login route is configured, users will be able to click a button and get redirected to it.

For detailed instructions on setting up your application to use Universal Login, check out our Quickstart guides and choose the one that best fits your chosen technologies. The Quickstart guides will walk you through all of the implementation steps.

Docs