Migrating to Lock v11
Lock v11 is designed for embedded login scenarios. It 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?
Lock can be used to implement authentication in different ways:
In your application, to implement embedded login.
In the Hosted Login Page, where you can use the configure Lock to behave in the way you need.
Migration to v11 will depend on how you are using Lock:
|Scenario||Migration to v11|
|In your application, to implement embedded login||Required|
|In a customized Hosted Login Page||Not Supported, keep using Lock 10 and/or Auth0.js|
If you decide to keep using Lock you will need to migrate to Lock v11.
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 them before upgrading.
- 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 v9
- Migrating from Lock v9 in Angular 1.x Applications
- Migrating from Lock v8
- Migrating from Lock v8 in Angular 1.x Applications
Disabling Legacy Lock API
After you update to Lock v11 and Auth0.js v9, it is advised that you turn off the Legacy Lock API toggle in the Dashboard. This will make your Auth0 tenant behave as if the API is no longer available. Starting on April 1st, this option will be forcibly disabled, so it is recommended you opt-in before that time to verify your configuration will work correctly.
You can find the setting in the Advanced section of Tenant Settings.
If Lock takes a lot of time to display the login options, it's because the Allowed Web Origins property is not correctly set. Please set it and try again.