Generate and Analyze HAR Files

A HAR (HTTP Archive) file shows the sequence of redirects that happen during a login transaction. It's an excellent tool for debugging authentication issues, as it can identify where things get stuck. A HAR file is a JSON formatted log of a web browser's interactions with a web server. If authentication isn't working as expected, you can generate and analyze HAR files to find issues. Including a HAR file in your support requests can help speed up the troubleshooting process.

1. Close all incognito windows in Google Chrome.

2. Open a new incognito window in Google Chrome.

3. Go to View > Developer > Developers Tools.

4. In the Developer Tools pane, choose the Network tab.

5. Check the Preserve Log checkbox to record all interactions.

6. Visit the page and complete the steps that trigger the issue.

7. Choose the Network tab.

8. Click the down arrow to export the HAR file.

9. Save the HAR file.

10. Next remove any sensitive information from the file.

    1. Open the HAR file with a text editor of your choice.

    2. Search for all instances of "Password".

    3. Replace these values with a placeholder value such as "*****".

    4. Save the HAR file.

1. Ensure that Show Develop menu in menu bar checkbox is checked under Safari > Preferences > Advanced.

2. Choose File > Open New Private Window.

3. Visit the web page where the issue occurs.

4. Choose Develop > Show Web Inspector. The Web Inspector window appears.

5. Complete the steps on the page that trigger the issue.

6. Select the Network tab.

7. Click Export on the upper right side of the pane.

8. Save the HAR file.

9. Next remove any sensitive information from the file.

   1. Open the HAR file with a text editor of your choice.

   2. Search for all instances of "Password".

   3. Replace these values with a placeholder value such as "*****".

   4. Save the HAR file.

1. Close all private windows in Firefox.

2. Open a new private window in Firefox.

3. Go to Tools > Developer > Network or ctrl-shift-E.

4. Visit the page and complete the steps that trigger the issue.

5. Choose the Network tab and right click and then select Save All As Har.

6. Save the HAR file.

7. Next remove any sensitive information from the file.

   1. Open the HAR file with a text editor of your choice.

   2. Search for all instances of "Password".

   3. Replace these values with a placeholder value such as "*****".

   4. Save the HAR file.

1. Close all InPrivate windows in Microsoft Edge.

2. Open a new InPrivate window (Ctrl + Shift + N).

3. Go to Settings and more (the ... icon) then choose More Tools > Developer Tools.

4. Start a profiling session on the Network tab of the Developer Tools toolbar.

5. Visit the page and complete the steps that trigger the issue.

6. Select Export as HAR (Ctrl+S) and save the HAR file.

7. Next remove any sensitive information from the file.

   1. Open the HAR file with a text editor of your choice.

   2. Search for all instances of "Password".

   3. Replace these values with a placeholder value such as "*****".

   4. Save the HAR file.

1. Close all InPrivate windows in Internet Explorer.

2. Open a new InPrivate window in Internet Explorer (ctrl+shift+P.)

3. Go to Tools > F12 Developer Options > Network.

4. Ensure Clear entries on navigate is switched off.

5. Visit the page and complete the steps that trigger the issue.

6. Choose the Network tab and select Export as HAR (Ctrl+S).

7. Save the HAR file.

8. Next remove any sensitive information from the file.

   1. Open the HAR file with a text editor of your choice.

   2. Search for all instances of "Password".

   3. Replace these values with a placeholder value such as "*****".

   4. Save the HAR file.

1. To view the HAR file, use a tool such as Google's HAR Analyzer.

2. Analyze the list of web requests captured in the HAR file. In particular, check the sequence of redirects to see how far you get in the authentication process. This helps identify where the issue is happening.

3. Compare the sequence of redirects to the expected sequence for your authentication flow.

   For example:

   • There should be a call to the /authorize endpoint to start the authentication flow.

   • There may be redirects to remote identity providers to prompt the user to log in.

   • Then there should be a redirect back to Auth0 /login/callback (https://login.auth0.com/login/callback).

   • Then there should be a redirect back to your application’s callback URL.

• Customer Support
• Open and Manage Support Tickets