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 as of April 1, 2018, and will at some point cease to work after this date. For clients who use Lock within an Auth0 login page, this migration is recommended; for client 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.
Disabling legacy Lock API
After you update to Lock v11 and/or 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 legacy API is no longer available. Starting on April 1, 2018, this option will be forcibly disabled, so it is recommended you opt-in before that time to verify that 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 could be because the Allowed Web Origins property is not correctly set.
The specified redirect_uri 'https://YOUR_APP_URL' does not have a registered domain.