New Universal Login vs. Classic Universal Login
If you decide to authenticate users with Auth0's Universal Login, you have a choice of two implementations:
New Universal Login offers a simpler and faster experience for end-users. All current and future Universal Login development work goes into the New Universal Login only. However, some Classic Universal Login features are not yet available in New Universal Login.
Classic Universal Login uses JavaScript controls for each page. Auth0 no longer adds new features to the Classic Universal Login.
This table compares features between the two:
Feature | New Universal Login | Classic Universal Login |
---|---|---|
Adopt new features without changing HTML | Yes | No |
Ongoing development and new feature additions | Yes | No |
Lightweight HTML | Yes | No |
JavaScript required | No | Yes |
Customization | Yes, using page templates or with just color and logo | Yes, using HTML, and only for login, multi-factor authentication (MFA), and password reset pages |
No-Code solution | Yes, using the No-Code Editor | No |
Passwordless authentication | Yes | Yes, with SMS or Email |
WebAuthn and device biometrics | Yes | No |
Web Content Accessibility Guidelines (WCAG) Compliance | Yes | No |
Organizations support | Yes | No |
Terms of service acceptance on signup | No | Yes |
Custom fields on signup | No | Yes |
Full localization | Yes, in these languages | Only for the login page |
Customizable localized text on all pages | Yes | No |
Email MFA | Yes | No |
Voice MFA | Yes | No |
Duo MFA | Yes, but Duo must be the only MFA factor enabled | Yes |
Buttons for enterprise connections | Yes | No |
Ability to disable self-service password recovery | Yes | Yes |
Custom URLs for password reset and user signup | Yes, using page templates and a custom-built password reset or signup page | Yes |
Kerberos support for AD/LDAP connections | No | Yes |
Requires exposing identity provider domains in a public endpoint | No | Yes |