Migrating to Lock v11
Lock v11 operates with enhanced security and removes dependencies that have been deprecated as per Auth0's roadmap. In some cases, these security enhancements may impact application behavior when upgrading from an earlier version of Lock.
Should I migrate to v11?
Everyone should migrate to v11. All previous versions are deprecated, and the Legacy Lock API was removed from service on August 6, 2018. For applications that use Lock within an Auth0 login page, this migration is recommended; for applications with Lock embedded within them, this migration is mandatory.
The documents below describe all the changes that you should be aware of when migrating from different versions of Lock. Make sure you go through the relevant guide(s) before upgrading.
- Migrating from the lock-passwordless widget
- Migrating from Lock v10
- Migrating from Lock v10 in Angular 1.x Applications
- Migrating from Lock v10 in Angular 2+ Applications
- Migrating from Lock v10 in React Applications
- Migrating from Lock v10 in Cordova Applications
- Migrating from Lock v9
- Migrating from Lock v9 in Angular 1.x Applications
- Migrating from Lock v8
- Migrating from Lock v8 in Angular 1.x Applications
Lock takes too long to display the login options
If Lock takes a lot of time to display the login options, it could be because the Allowed Web Origins property is not correctly set.
I upgraded but I still get deprecation warnings in the logs
You have already migrated to Lock 11 but you still see this error in your logs:
These deprecation notices most likely originate from a user visiting the Universal Login page directly without initiating the authentication flow from your app. This can happen if a user bookmarks the login page directly. After August 6, 2018, these users will not be able to log in.
Check out the Deprecation Error Reference for more information on deprecation related errors.