Troubleshooting Federated Login
If your application doesn't work the first time, clear your browser history and cookies before you test again. If you don't, the browser may not pick up the latest version of your HTML page, or it may have outdated cookies that impact execution.
To troubleshoot Federated Login:
- Capture an HTTP trace of the interaction: Use any of the available tools to capture the HTTP traffic from your browser for analysis.
- Search for HTTP Trace.
- Capture the login sequence from start to finish, and analyze the sequence of GETs to determine how much of the sequence was successful.
- See a redirect from your original site to the service provider and then to the identity provider.
- A post of credentials if you had to log in.
- A redirect back to the callback URL or the service provider.
- Finally, a redirect to the callback URL specified in your application.
- Ensure the cookies and JavaScript are enabled for your browser.
- Check to make sure that the callback URL specified by your application in its authentication request is listed in the Allowed Callback URLs field.
- The http://samltool.io tool can decode a SAML assertion and is a useful debugging tool.