An authentication transaction often has several parts. Auth0 provides methods so you can try individual parts of the transaction to help you find the possible source of the problem.
Most identity provider connections have a TRY button to see if the connection is working. If that fails, you can debug the connection without involving the rest of the application. If the connection works, then you can start debugging the application.
- Use the TRY button on a connection to test just the connection.
- If the test with the TRY button fails, you know it is not an issue with your application but rather something with the connection configuration or the connection provider.
- Check the response from the test with the TRY button to see if the response contains a useful error message or other information.
- Try logging into the same service through a different path.
- If the same issue occurs you’ll know it’s some sort of issue with the account
- If a test with the TRY button fails for a custom DB connection, it is frequently caused by an issue in the custom DB scripts. Putting console.log statements into them and viewing output in the Console Log can help debug them.
Verify external service dependencies
- If your authentication uses external services, like social identity providers, and it suddenly stops working, check external services status.
- If a connection is not working, even with the TRY button, check the connection.
See Log Events for more details on each of the log events that can help you troubleshoot issues.