We are actively migrating customers to new behaviors for all Deprecations listed below. Please review these carefully to ensure you've taken any necessary steps to avoid service disruptions. See Deprecation and End Of Life to learn more about this process.
|Feature/Behavior||Deprecated||End Of Life Date||Details|
|User Search v2||6 June 2018||30 June 2019||User Search v2 is being deprecated and you may be required to take action before June 30, 2019. A migration guide is available to walk you through the steps required. Notifications have been and will continue to be sent to customers that need to complete this migration.
User Search v3
User Search v3 - Query Syntax
User Search Best Practices
User Search v2 to v3 Migration Guide
||30 April 2019||30 July 2019||On April 30th 2019, Facebook deprecated the use of the 'Social Context’ field for new applications.|
|Tenant Logs Search v2||21 May 2019||
Free: 9 July 2019
Developer: 20 August 2019
Developer Pro: 20 August 2019
Enterprise: 4 November 2019
|To provide our customers with the most reliable and scalable solution, Auth0 has deprecated Tenant Logs Search Engine v2 in favor of v3. Auth0 is proactively migrating customers unaffected by this change, while those who are potentially affected are being notified to opt in for v3 during the provided grace period. See the migration guide for more information.|
|Node.js v4 Extensibility Runtime||17 April 2019||30 June 2019||
The Webtask engine powering Auth0 extensibility points currently uses Node 4. Beginning 30 April 2018, Node.js v4 will no longer be under long-term support (LTS). This means that critical security fixes will no longer be back-ported to this version. As such, Auth0 will be migrating the Webtask runtime from Node.js v4 to Node.js v8.
On 17 April 2018 we will make the Node 8 runtime available for extensibility to all public cloud customers. You will be provided a migration switch that allows you to control your environment's migration to the new runtime environment.
For more information on this migration and the steps you should follow to upgrade your implementation, see Migration Guide: Extensibility and Node.js v8.