SAML Authentication Issue with JumpCloud - Unsupported HTTP-Redirect Binding #7344
mjmanas0699
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Team,
I’m trying to integrate Redash with JumpCloud SAML authentication, but I keep getting an error related to unsupported bindings:
[ERROR][saml2.mdstore] Unsupported binding: urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect (Jumpcloud) ... saml2.client_base.SignOnError: {'message': 'No supported bindings available for authentication', 'bindings_to_try': ['urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect'], 'unsupported_bindings': ['urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect']}I have verified that my JumpCloud metadata.xml explicitly specifies:
<md:SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://sso.jumpcloud.com/saml2/redash"/>However, Redash still seems to be trying HTTP-Redirect instead of HTTP-POST, leading to authentication failure. I'm i missing something here?
Any help or guidance would be greatly appreciated! Thanks in advance.
Logs:
Beta Was this translation helpful? Give feedback.
All reactions