Skip to content
English
More support Sign in
EveryCloud
  • There are no suggestions because the search field is empty.

Okta – Exporting Browser Log Files for Troubleshooting

How to collect browser console and network logs for Okta login and SSO issues

Link to article

https://support.okta.com/help/s/article/Exporting-browser-log-files-for-troubleshooting?language=en_US

Link to video:

 

Overview

When troubleshooting Okta login, MFA, or SSO issues, browser logs can provide valuable diagnostic information. Exporting console and network logs helps identify authentication failures, redirect issues, blocked scripts, or policy errors.

This guide explains how to collect browser logs for support investigation.

Applies to

  • Okta Workforce Identity

  • Okta SSO integrations

  • Login, MFA, and redirect-related issues

  • Modern web browsers (Chrome, Edge, Firefox)

Before You Start

  • Reproduce the issue while Developer Tools are open.

  • Ensure logging begins before attempting login.

  • Do not include sensitive information when sharing logs externally.

Google Chrome / Microsoft Edge (Chromium-based)

To Collect Network Logs (HAR File)

  1. Open the browser.

  2. Press F12 or right-click the page and select Inspect.

  3. Go to the Network tab.

  4. Enable:

    • “Preserve log”

    • “Disable cache”

  5. Reproduce the issue.

  6. Right-click anywhere in the Network panel.

  7. Select Save all as HAR with content.

  8. Save the file securely.

To Collect Console Logs

  1. Open Developer Tools (F12).

  2. Go to the Console tab.

  3. Reproduce the issue.

  4. Right-click inside the Console.

  5. Choose Save as… (or manually copy errors if needed).

Mozilla Firefox

To Collect Network Logs

  1. Press F12 to open Developer Tools.

  2. Go to the Network tab.

  3. Enable Persist Logs.

  4. Reproduce the issue.

  5. Click the gear icon (⚙).

  6. Choose Save All As HAR.

To Collect Console Logs

  1. Open Developer Tools.

  2. Go to the Console tab.

  3. Reproduce the issue.

  4. Right-click and select Export Visible Messages (if available), or copy errors manually.

What to Look For

Common indicators in logs:

  • 403 or 401 HTTP errors

  • CORS errors

  • Redirect loops

  • Failed API calls

  • Blocked scripts

  • Network timeouts

Logs often help identify whether the issue is:

  • Policy-related

  • Network-related

  • Browser-related

  • Application configuration-related

Impact

Without browser logs:

  • Login and SSO issues may be difficult to diagnose.

  • Policy or redirect failures may not be visible from the user interface.

  • Support resolution time may increase.

Action Required

  • Capture both Network (HAR) and Console logs where possible.

  • Reproduce the issue while logging is enabled.

  • Provide logs securely to support for review.

  • Avoid sending logs via insecure channels if they contain sensitive information.

Additional Information

Browser logs may contain:

  • Session identifiers

  • Request URLs

  • Tenant information

Ensure logs are handled according to your organisation’s data protection policies.