Okta sso troubleshoot page #490
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for docsv1 ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds troubleshooting documentation for Okta SSO integration across three OpenMetadata versions (v1.9.x, v1.10.x, and v1.11.x-SNAPSHOT). The documentation addresses a common issue where users experience a spinning wheel timeout when configuring Okta authentication, caused by incorrect or excessive callback URL configurations.
Key Changes
- New troubleshooting guide explaining how to resolve spinning wheel timeout errors with Okta SSO
- Guidance on ensuring callback URLs are reachable and properly configured
- Code examples showing the correct redirect URI configuration
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 9 comments.
| File | Description |
|---|---|
| content/v1.9.x/deployment/security/okta/troubleshooting.md | Adds Okta troubleshooting guide for v1.9.x with instructions on fixing callback URL issues |
| content/v1.10.x/deployment/security/okta/troubleshooting.md | Adds Okta troubleshooting guide for v1.10.x (identical content to v1.9.x) |
| content/v1.11.x-SNAPSHOT/deployment/security/okta/troubleshooting.md | Adds Okta troubleshooting guide for v1.11.x-SNAPSHOT (identical content to other versions) |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| 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. |
There was a problem hiding this comment.
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. |
|
|
||
| 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. |
There was a problem hiding this comment.
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. |
|
|
||
| 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. |
There was a problem hiding this comment.
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. |
|
|
||
| # FAQ: Security with Okta | ||
|
|
||
| ## How to resolve spinnging timeout error when connecting to OpenMetadata with Okta SSO? |
There was a problem hiding this comment.
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? |
|
|
||
| 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. |
There was a problem hiding this comment.
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. |
|
|
||
| # FAQ: Security with Okta | ||
|
|
||
| ## How to resolve spinnging timeout error when connecting to OpenMetadata with Okta SSO? |
There was a problem hiding this comment.
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? |
|
|
||
| # FAQ: Security with Okta | ||
|
|
||
| ## How to resolve spinnging timeout error when connecting to OpenMetadata with Okta SSO? |
There was a problem hiding this comment.
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? |
|
|
||
| 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. |
There was a problem hiding this comment.
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. |
|
|
||
| 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. |
There was a problem hiding this comment.
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding troubleshooting guide to okta docs to alleviate spinning wheel issue encountered while setting up sso