-
-
Notifications
You must be signed in to change notification settings - Fork 301
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.
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
Support for singleSignOnService SSO HTTP-POST binding #146
Comments
On this toolkit, only the SAMLResponse when SSO must to be received as POST, rest of SAML messages use the HTTP-Redirect binding. That said, take a look on this PR. The login method deflate and URLencode (on the redirect method) the SAMLRequest value. You can use
to get the AuthNRequest value that you want. |
Thank you so much for the help.. especially for the clue on setting deflate to false on the get_request. I will try it out and let you know |
Hello,
I have an IDP that only supports the urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST for the singleSignOnService to initiate the SP login flow.
In looking at the code, it appears the library is designed to work with HTTP-Redirect only. Can you please confirm that HTTP-Redirect is the only currently supported binding?
Also, I am curious if the auth.login() method currently URLEncodes the SAMLRequest value? I am trying to use the results of this method to include in an xHTML form to post the SAMLRequest value to the IDP.
"singleSignOnService": {
"binding": "urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST",
"url": "blah"
}
The text was updated successfully, but these errors were encountered: