Skip to content

Commit 817eaec

Browse files
committed
feat: add redirection uri errors in FAQ
1 parent e80d073 commit 817eaec

File tree

1 file changed

+12
-1
lines changed
  • content/docs/account-settings/authentication

1 file changed

+12
-1
lines changed

content/docs/account-settings/authentication/FAQs.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,4 +12,15 @@ This error means that the email address you are using does not belong to a domai
1212

1313
**For NocoDB Cloud:** Yes. In addition to configuring Google OAuth or other SSO providers, you must also verify your domain in the SSO settings. This is done by adding your domain and verifying it by adding the provided TXT record to your DNS. Only after domain verification will users from that domain be able to sign in via SSO.
1414

15-
**For NocoDB Self-hosted/On-prem:** Domain verification is not required. You can configure SSO providers without verifying your domain via DNS.
15+
**For NocoDB Self-hosted/On-prem:** Domain verification is not required. You can configure SSO providers without verifying your domain via DNS.
16+
17+
## Why do I get a redirection/callback URL or URI error when setting up SSO?
18+
19+
This error usually means that the Redirect URL (sometimes called Callback URL or Redirect URI) configured in your identity provider does not exactly match the one provided by NocoDB. Common reasons include:
20+
- Typo or extra spaces in the URL/URI
21+
- Using HTTP instead of HTTPS (or vice versa)
22+
- Not including the full path as required
23+
- Registering the wrong environment (e.g., using a local URL for production)
24+
- Forgetting to update the Redirect URL after changing your NocoDB domain
25+
26+
**Solution:** Always copy and paste the exact Redirect URL/URI provided by NocoDB into your identity provider's configuration. Any mismatch will result in an error during authentication.

0 commit comments

Comments
 (0)