Universal Login vs. Classic Login
Auth0 Universal Login provides the essential feature of an authorization server: the login flow. When a user needs to prove their identity to gain access to your application, you can redirect them to Universal Login and let Auth0 handle the authentication process.
Universal Login is Auth0's primary hosted login solution. Universal Login features easy-to-use customization tools and promotes a simpler, faster experience for end-users. Alternatively, Auth0 also supports Classic Login, a hosted login experience that uses JavaScript controls for customization.
To help you choose the best solution for your needs, the table below compares the features of both login experiences.
Feature | Universal Login | Classic 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 the no-code editor | 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 |
Email magic link | No | Yes |
Passkeys | Yes | No |
WebAuthn and device biometrics | Yes | No |
Web Content Accessibility Guidelines (WCAG) Compliance | Yes | No |
Organizations support | Yes | No |
Terms of service acceptance on signup | Yes | Yes |
Custom fields on signup | Yes | 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 |
MFA customization with Actions | Yes | No |
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 |