When Auth0 deprecates features, errors or notices appear in the tenant logs to indicate that applications use the deprecated features. Search the logs using the Auth0 Dashboard or the Management API to identify deprecation-related messages and resolve the underlying causes.

NOTE: The log retention period depends on the account's subscription level.

• Auth0
• Logs
• Troubleshooting

How are deprecation errors checked using the Auth0 Dashboard?

Search for deprecation-related messages in the Auth0 Dashboard by navigating to the Logs and querying for the deprecation note type.

NOTE: A Deprecation Notice message appears only once per hour (the first time the error occurs within that hour) rather than for each authentication transaction involving the deprecated feature.

1. Navigate to Monitoring > Logs in the Auth0 Dashboard and search for deprecation-related messages by entering type:depnote in the query box. A list of deprecation-related warning messages appears if any exist. The Description field provides information on the particular deprecated feature used.
2. Select the link in the Type column for each item to view additional information, such as the client ID, which identifies the client application using the deprecated feature.
3. Select the log entries and choose the Context Data tab to view details about the item.

How are deprecation errors checked using the Management API?

Search for deprecation-related messages using the Management API by querying the search log events endpoint for the deprecation note type.

1. Navigate to the Management API and obtain an API token.
2. Navigate to Logs > Search log events on the left and scroll down to Parameters.
3. Enter type:"depnote" in the q field.
4. Select TRY. The Client ID field in the results indicates which application on the tenant uses the deprecated feature.

What are common deprecation log messages?

Review the following deprecation log messages to determine the cause and resolution for specific items.

Legacy Lock API

Review the following details to resolve the Legacy Lock API deprecation error:

• Log entry: up-idp-initiated
• Error Message: Legacy Lock API: This feature is being deprecated. Please refer to our documentation to learn how to migrate your application.
• Cause: Tenant log entries regarding the Legacy Lock API might include the referrer and information about the SDK used.
• Resolution: Use this information to determine if any applications use outdated libraries.

SSOdata endpoint

Review the following details to resolve the SSOdata endpoint deprecation error:

• Log entry: ssodata
• Error Message: SSOdata endpoint: This feature is being deprecated. Please refer to our documentation to learn how to migrate your application.
• Cause: The /ssodata endpoint is called directly, or old versions of the embedded Lock or Auth0.js SDK are used to call a function that calls the /ssodata endpoint.
• Resolution: Update the Lock SDK or Auth0.js SDK to the most recent version.

Related References

• Verify Connections to Troubleshoot Auth0 Issues
• Verify the Platform to Troubleshoot Auth0 Issues
• Verify the Domain to Troubleshoot Auth0 Issues
• Verify Rules to Troubleshoot Auth0 Issues
• Check Error Messages to Troubleshoot Auth0 Issues
• Log Data Retention
• Logs