Skip to content

Okta sso troubleshoot page #490

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
PubChimps wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Okta sso troubleshoot page #490

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4636e3c
adding okta troubleshooting guide to docs
Oct 10, 2025
cdc8da3
updating okta troubleshooting guide to docs
Oct 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions content/v1.10.x/deployment/security/okta/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
---
title: Fix Timeout When Using Okta SSO
description: Learn how to resolve errors in OpenMetadata when using Okta, including a spinning wheel timeout with Okta redirects
slug: /deployment/security/okta/troubleshooting
collate: false
---

# FAQ: Security with Okta

## How to resolve spinnging timeout error when connecting to OpenMetadata with Okta SSO?
Copy link

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo in the question heading: "spinnging" should be "spinning".

Suggested change
## How to resolve spinnging timeout error when connecting to OpenMetadata with Okta SSO?
## How to resolve spinning timeout error when connecting to OpenMetadata with Okta SSO?

Copilot uses AI. Check for mistakes.

If you're using Okta to authenticate OpenMetadata with SSO, it may redirect to a blank screen with a spinning wheel, indicating a redirect issue.

### Resolution

To allow Okta to authenticate and redirect to OpenMetadata properly:

1. Ensure your callback URLs are pointing to OpenMetadata that Okta can reach. [Our guide](/deployment/security/okta/auth-code-flow) uses `localhost:8585` if you are not hosting OpenMetadata locally, you will need to update your sign-in redirect URIs, and possibly your sign-out redict URIs and base URIs if you have set those.
Copy link

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo: "redict" should be "redirect".

Suggested change
1. Ensure your callback URLs are pointing to OpenMetadata that Okta can reach. [Our guide](/deployment/security/okta/auth-code-flow) uses `localhost:8585` if you are not hosting OpenMetadata locally, you will need to update your sign-in redirect URIs, and possibly your sign-out redict URIs and base URIs if you have set those.
1. Ensure your callback URLs are pointing to OpenMetadata that Okta can reach. [Our guide](/deployment/security/okta/auth-code-flow) uses `localhost:8585` if you are not hosting OpenMetadata locally, you will need to update your sign-in redirect URIs, and possibly your sign-out redirect URIs and base URIs if you have set those.

Copilot uses AI. Check for mistakes.
Copy link

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing period at the end of the sentence. Also, there's a missing comma after "localhost:8585" for clarity.

Suggested change
1. Ensure your callback URLs are pointing to OpenMetadata that Okta can reach. [Our guide](/deployment/security/okta/auth-code-flow) uses `localhost:8585` if you are not hosting OpenMetadata locally, you will need to update your sign-in redirect URIs, and possibly your sign-out redict URIs and base URIs if you have set those.
1. Ensure your callback URLs are pointing to OpenMetadata that Okta can reach. [Our guide](/deployment/security/okta/auth-code-flow) uses `localhost:8585`, if you are not hosting OpenMetadata locally, you will need to update your sign-in redirect URIs, and possibly your sign-out redict URIs and base URIs if you have set those.

Copilot uses AI. Check for mistakes.
2. Keep only the callback URLs that OpenMetadata actually uses:

```
redirect_uris = [
"http://localhost:8585/callback",
"http://localhost:8585/silent-callback" # Only if needed for silent refresh
]
```

OpenMetadata isn't configured to handle additional endpoints, so the frontend will spin indefinitely.
28 changes: 28 additions & 0 deletions content/v1.11.x-SNAPSHOT/deployment/security/okta/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
---
title: Fix Timeout When Using Okta SSO
description: Learn how to resolve errors in OpenMetadata when using Okta, including a spinning wheel timeout with Okta redirects
slug: /deployment/security/okta/troubleshooting
collate: false
---

# FAQ: Security with Okta

## How to resolve spinnging timeout error when connecting to OpenMetadata with Okta SSO?
Copy link

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo in the question heading: "spinnging" should be "spinning".

Suggested change
## How to resolve spinnging timeout error when connecting to OpenMetadata with Okta SSO?
## How to resolve spinning timeout error when connecting to OpenMetadata with Okta SSO?

Copilot uses AI. Check for mistakes.

If you're using Okta to authenticate OpenMetadata with SSO, it may redirect to a blank screen with a spinning wheel, indicating a redirect issue.

### Resolution

To allow Okta to authenticate and redirect to OpenMetadata properly:

1. Ensure your callback URLs are pointing to OpenMetadata that Okta can reach. [Our guide](/deployment/security/okta/auth-code-flow) uses `localhost:8585` if you are not hosting OpenMetadata locally, you will need to update your sign-in redirect URIs, and possibly your sign-out redict URIs and base URIs if you have set those.
Copy link

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing period at the end of the sentence. Also, there's a missing comma after "localhost:8585" for clarity.

Suggested change
1. Ensure your callback URLs are pointing to OpenMetadata that Okta can reach. [Our guide](/deployment/security/okta/auth-code-flow) uses `localhost:8585` if you are not hosting OpenMetadata locally, you will need to update your sign-in redirect URIs, and possibly your sign-out redict URIs and base URIs if you have set those.
1. Ensure your callback URLs are pointing to OpenMetadata that Okta can reach. [Our guide](/deployment/security/okta/auth-code-flow) uses `localhost:8585`, if you are not hosting OpenMetadata locally, you will need to update your sign-in redirect URIs, and possibly your sign-out redict URIs and base URIs if you have set those.

Copilot uses AI. Check for mistakes.
Copy link

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo: "redict" should be "redirect".

Suggested change
1. Ensure your callback URLs are pointing to OpenMetadata that Okta can reach. [Our guide](/deployment/security/okta/auth-code-flow) uses `localhost:8585` if you are not hosting OpenMetadata locally, you will need to update your sign-in redirect URIs, and possibly your sign-out redict URIs and base URIs if you have set those.
1. Ensure your callback URLs are pointing to OpenMetadata that Okta can reach. [Our guide](/deployment/security/okta/auth-code-flow) uses `localhost:8585` if you are not hosting OpenMetadata locally, you will need to update your sign-in redirect URIs, and possibly your sign-out redirect URIs and base URIs if you have set those.

Copilot uses AI. Check for mistakes.
2. Keep only the callback URLs that OpenMetadata actually uses:

```
redirect_uris = [
"http://localhost:8585/callback",
"http://localhost:8585/silent-callback" # Only if needed for silent refresh
]
```

OpenMetadata isn't configured to handle additional endpoints, so the frontend will spin indefinitely.
28 changes: 28 additions & 0 deletions content/v1.9.x/deployment/security/okta/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
---
title: Fix Timeout When Using Okta SSO
description: Learn how to resolve errors in OpenMetadata when using Okta, including a spinning wheel timeout with Okta redirects
slug: /deployment/security/okta/troubleshooting
collate: false
---

# FAQ: Security with Okta

## How to resolve spinnging timeout error when connecting to OpenMetadata with Okta SSO?
Copy link

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo in the question heading: "spinnging" should be "spinning".

Suggested change
## How to resolve spinnging timeout error when connecting to OpenMetadata with Okta SSO?
## How to resolve spinning timeout error when connecting to OpenMetadata with Okta SSO?

Copilot uses AI. Check for mistakes.

If you're using Okta to authenticate OpenMetadata with SSO, it may redirect to a blank screen with a spinning wheel, indicating a redirect issue.

### Resolution

To allow Okta to authenticate and redirect to OpenMetadata properly:

1. Ensure your callback URLs are pointing to OpenMetadata that Okta can reach. [Our guide](/deployment/security/okta/auth-code-flow) uses `localhost:8585` if you are not hosting OpenMetadata locally, you will need to update your sign-in redirect URIs, and possibly your sign-out redict URIs and base URIs if you have set those.
Copy link

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing period at the end of the sentence. Also, there's a missing comma after "localhost:8585" for clarity.

Suggested change
1. Ensure your callback URLs are pointing to OpenMetadata that Okta can reach. [Our guide](/deployment/security/okta/auth-code-flow) uses `localhost:8585` if you are not hosting OpenMetadata locally, you will need to update your sign-in redirect URIs, and possibly your sign-out redict URIs and base URIs if you have set those.
1. Ensure your callback URLs are pointing to OpenMetadata that Okta can reach. [Our guide](/deployment/security/okta/auth-code-flow) uses `localhost:8585`, if you are not hosting OpenMetadata locally, you will need to update your sign-in redirect URIs, and possibly your sign-out redirect URIs and base URIs if you have set those.

Copilot uses AI. Check for mistakes.
Copy link

Copilot AI Dec 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo: "redict" should be "redirect".

Suggested change
1. Ensure your callback URLs are pointing to OpenMetadata that Okta can reach. [Our guide](/deployment/security/okta/auth-code-flow) uses `localhost:8585` if you are not hosting OpenMetadata locally, you will need to update your sign-in redirect URIs, and possibly your sign-out redict URIs and base URIs if you have set those.
1. Ensure your callback URLs are pointing to OpenMetadata that Okta can reach. [Our guide](/deployment/security/okta/auth-code-flow) uses `localhost:8585` if you are not hosting OpenMetadata locally, you will need to update your sign-in redirect URIs, and possibly your sign-out redirect URIs and base URIs if you have set those.

Copilot uses AI. Check for mistakes.
2. Keep only the callback URLs that OpenMetadata actually uses:

```
redirect_uris = [
"http://localhost:8585/callback",
"http://localhost:8585/silent-callback" # Only if needed for silent refresh
]
```

OpenMetadata isn't configured to handle additional endpoints, so the frontend will spin indefinitely.