This article describes how to record, save, and export log files from a web browser for troubleshooting purposes.

• Okta Classic Engine
• Chrome
• Firefox

Each browser provides a Developer Console that can provide valuable insight to Okta support when troubleshooting a variety of Okta-related issues. If support requests browser logs or a HAR file, please refer to the video or the steps below:

 

DISCLAIMER: When capturing user logins via the browser developer console logs, the username/password will be captured in plain text within the log file and will be visible to anyone with access to the file. This can also occur with active session cookies. It is recommended to sanitize the HAR file to replace any secrets before uploading it to Okta Support.

NOTE: Developer tools will only capture traffic from the tab for which it is open. If recreating the issue results in new tabs being opened during the flow, the traffic will only be captured on the original tab. Example: IDP initiated SAML login flow. When clicking the application tile in the Okta Dashboard, a new tab will open, and SAML traffic will occur on the new tab. Please see How to Capture SAML Traffic with Browser Tools Across Multiple Tabs for more details.

Chrome

1. In Chrome, hit the F12 key or Ctrl-Shift-I to launch Chrome's Developer Tools console.  By default, the panel will open on the right side of the Chrome window.
2. In the Developer Tools panel, click on the Network tab.
3. Check the Preserve log option and the Disable Cache option.
   1. Ensure that the circle icon in the upper-left of the Developer Tools pane is red, which indicates that the browser activity is now being recorded as a log.  If the circle is black, click it until it becomes red.
   2. If any events appear in the Developer Tools panel, click the Clear button to the right of the circle icon to remove them from the log.
4. Navigate to the page in Okta where the issue is being encountered and perform whatever steps are necessary to reproduce it.
5. When the issue has been successfully reproduced, click the down arrow in the Developer Tools panel to save the HAR file.
6. Upload the HAR file to the Support Portal to sanitize the HTTP traces automatically.  Refer to How to Sanitize a HTTP Trace File Automatically.

As of Google Chrome 130, the contents of a HAR file are sanitized during export. Okta Support may require some of the sanitized content to be present during troubleshooting. To enable unsanitized HAR collection:

1. Navigate to Settings > Preferences > Network.
2. Select the "Allow to generate HAR with sensitive data" check box.
3. When exporting a HAR file, click and hold the left mouse button over the down arrow. Chrome will provide an option to export with sensitive data.

NOTE: Uploading the HAR file in Step #6 above will still sanitize the HAR contents, but keep data like cookie names with sanitized values to aid support in troubleshooting.

Firefox

1. In Firefox, hit Ctrl-Shift-E to open the Web Developer Network console.  By default, the panel will open at the bottom of the Firefox window.
2. Navigate to the gear icon and ensure that the Persist Logs option is checked.
3. Navigate to the page in Okta where the issue is occurring and perform the necessary steps to reproduce it.
4. When the issue has been successfully reproduced, right-click on any of the logged events in the Web Developer panel and click Save All As HAR.

5. Upload the HAR file to the Support Portal to automatically sanitize the HTTP traces. Refer to How to Sanitize a HTTP Trace File Automatically.

Viewing HAR files in Fiddler

While HAR files can be opened using any text editor, Fiddler presents them in a much more useful and readable layout.  To open HAR files with Fiddler:

1. Launch Fiddler.
2. Click File > Import Sessions...
3. In the Select Import Format window that appears, select HTTPArchive in the drop-down box and click Next.
4. Select the HAR file that was saved in the previous steps and click Open.

How to Remove the Password From a Generated .har File

NOTE: The support center portal now automatically clears out users' passwords. Below is for extra caution.

1.  After generating the .har file, open it in a text editor and navigate to the line where the password is located. Sample line content:

   ],
   
   "headersSize": 8370,
   
   "bodySize": 106,
   
   "postData": {
   
   "mimeType": "application/json",
   
   "text": "{\"credentials\":{\"passcode\":\"[YourPassword]\"},\"stateHandle\":\"........................................................\"}"
   
   }

2. Change or remove the password.
3. Save it.
4. Upload the HAR file to the Support Portal to sanitize the HTTP traces automatically. Refer to How to Sanitize a HTTP Trace File Automatically.

Related References

• How to Sanitize a HTTP Trace File Automatically
• Sanitizing HTTP Traces
• Google Chrome 130 Update