---
title: Generate and analyze HAR files
slug: opti-id/docs/generate-and-analyze-har-files
docTags: 
createdAt: 2026-07-30T20:38:25.269Z
---

A HAR (HTTP Archive) file shows the sequence of redirects that happen during a login transaction. It is an excellent tool for debugging authentication issues because 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 is not working as expected, you can generate and analyze HAR files to find issues. Including a HAR file in your [support request](https://support.auth0.com/) can help speed up the troubleshooting process.

:::hint{type="warning"}
**Important**

Before sending the HAR file to Opti ID support, ensure that you remove or obfuscate any sensitive information (such as passwords and client secrets) using a text editor.
:::

## Generate HAR files with browsers

### Google Chrome

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. Select the **Preserve Log** checkbox to record 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. Remove any sensitive information from the file.
    1. Open the HAR file with a text editor.
    2. Search for all instances of `"Password"`.
    3. Replace these values with a placeholder value such as `"*****"`.
    4. Save the HAR file.

### Safari

1. Go to **Safari > Preferences > Advanced** and ensure that **Show Develop menu in menu bar** checkbox is selected.
2. Choose **File > Open New Private Window**.
3. Choose **Show Web Inspector** in the **Developer** menu, then go to the **Network** tab.
4. To the right of **All** near the top-left of the **Web Inspector**, click **Filter** and choose **Preserve Log.**
5. Go to the web page where the issue occurs.
6. Choose **Develop > Show Web Inspector**. The Web Inspector window displays.
7. Complete the steps on the page that trigger the issue.
8. Select the **Network** tab.
9. Click **Export** on the upper right side of the pane.
10. Save the HAR file.
11. Remove any sensitive information from the file.
    1. Open the HAR file with a text editor.
    2. Search for all instances of `"Password"`.
    3. Replace these values with a placeholder value such as `"*****"`.
    4. Save the HAR file.

### Firefox

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. Click the **Network** tab and choose **Persist Logs.**
5. Visit the page and complete the steps that trigger the issue.
6. Choose the **Network** tab and right-click to select **Save All As Har**.
7. Save the HAR file.
8. Remove any sensitive information from the file.
   1. Open the HAR file with a text editor.
   2. Search for all instances of `"Password"`.
   3. Replace these values with a placeholder value such as `"*****"`.
   4. Save the HAR file.

### Microsoft Edge

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. Remove any sensitive information from the file.
   1. Open the HAR file with a text editor.
   2. Search for all instances of `"Password"`.
   3. Replace these values with a placeholder value such as `"*****"`.
   4. Save the HAR file.

## Analyze HAR files

1. To view the HAR file, use a tool such as [Google's HAR Analyzer](https://toolbox.googleapps.com/apps/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 Opti ID Okta instance.
   - Then there should be a redirect back to your application’s callback URL.
4. Send this .har file to Opti ID support for further troubleshooting.