Hey, We have a client that configured SSO using OK...
# ask-a-descoper
s
Hey, We have a client that configured SSO using OKTA(OIDC) and claim that some users managed to login successfully, but some are stuck in a logic loop, both when trying from okta and from our app screen. I can't see any related logic in audit or troubleshooting logs and wonder how I should processed from here.
✅ 1
d
Check OIDC Configuration and Audit Logs Since some users can log in while others are stuck in a loop, this points to a configuration or callback URL issue. The Audit and Troubleshoot page is your best starting point. Debug Steps 1. Check the Audit page at https://app.descope.com/audits for SSO-related events 2. Look for failed authentication attempts and examine the OIDC userinfo endpoint responses 3. Verify these OIDC settings in your tenant configuration: - Callback URL matches exactly between Okta and Descope - Client ID and Secret are correct - Redirect URIs are properly configured in both systems - No URL encoding issues or trailing slashes Common Loop Causes • Callback URL mismatch between Okta configuration and Descope settings • Missing or incorrect redirect URI configuration • Token endpoint accessibility issues • Scope configuration problems Check if the users experiencing loops have any common attributes (domain, group membership, etc.) that might affect attribute mapping or user provisioning. [] [] [] SSO User and Group Mapping Guide | Descope Documentation SSO Troubleshooting | Descope Documentation SSO with OIDC Provider | Descope Documentation
r
Can you dm me your project id
✅ 1
s
I got a video from our client confirming this that I can share on a call in private. Is someone available to assist on this by any chance?
r
Hi @Sharon Great Can we connect in 15 min?
s
Sure, thanks
r
@Sharon JFI As we discussed on call I am checking why few of sso user is not able to login into descope with okta fast.
s
Any chance anyone else is available right now to assist on this issue? It's getting pretty urgent at this point.
r
Hi @Sharon As we discussed due to wrong redirect configuration url it is causing issue. and now it is working please confirm
s
Seems so, yes