In our previous notification, we informed you that certain endpoints (/usernamepassword/login and /ssodata) would be removed from service on April 1, 2018. This update is to notify you that the Removal of Service date for those endpoints has been extended to July 16, 2018.
We still encourage you to migrate your applications to the latest version of Lock 11 and Auth0.js 9 as soon as possible in order to ensure that your applications continue to function properly. Please refer to our migration guides for instructions on upgrading your Auth0 implementation if necessary.
This a follow-up to our “Auth0 Roadmap and Deprecations” notification from late December 2017, to remind you of the potential need to upgrade your applications and also to inform you of changes in some of our announced endpoint deprecations.
As we previously notified customers, we are deprecating certain APIs (usernamepassword/login, /ssodata) used by Lock.js 7, 8, 9 and 10 and and auth0.js, 6, 7, 8.
If you’re currently using our Hosted Login Page, no action is needed from you. Otherwise, if you embed Lock or auth0.js in your applications, you should update them before April 1, 2018.
How to Upgrade to Lock 11 & Auth0.js 9
Listed below are links to a webinar, documents and videos with further details and guidance on the upgrade process to Lock 11 and Auth0.js 9.
- Guides: migrate from auth0.js 6, 7, 8 angular or react
- Guides: migrate from Lock 8, 9, 10, angular or react
- Video: migrate from auth0.js 8 to 9 (most common case)
- Video: migrate from Lock 10 to 11 (most common case)
- Webinar: view on-demand migration webinar
Change in Plans for Other Deprecations
In our roadmap notification in late December, we also announced the planned deprecation of the following endpoints:
- Usage of id_token on Management API
These endpoints are proprietary, non-standards based solutions to authentication and identity management. It has been our intention to encourage the adoption of standards-based solutions and reduce or eliminate the need for proprietary protocols, and this led to our plans for these announced deprecations.
However, based on customer feedback, we have adjusted our plans and will continue to maintain and support the above existing proprietary endpoints. We will also publish new guidance on the most effective ways to transition your applications to standards-based protocols. In the event that we need to make security enhancements to any of these legacy endpoints, we will announce timeframes and guidelines for any required changes at that time.
If you have any questions about the above, please post your question in the “Migrations / Deprecations” section of the Auth0 Community site. Thank you for your continuing partnership with Auth0.
Head of Product