-
Notifications
You must be signed in to change notification settings - Fork 433
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
service provider: implement HTTP-POST binding #1
Comments
crewjam
changed the title
implement service provider HTTP-POST transport
service provider: implement HTTP-POST transport
Dec 1, 2015
crewjam
changed the title
service provider: implement HTTP-POST transport
service provider: implement HTTP-POST binding
Dec 1, 2015
fixed in c058931 |
canthefason
added a commit
to launchpadcentral/saml
that referenced
this issue
Aug 16, 2017
crewjam
pushed a commit
that referenced
this issue
Oct 29, 2019
* - Check if IDP-initiated login is allowed and if so assume that the RelayState is a deep-link. - Guard against an IDP-initiated request that may not have the request ID in the claims. - Attempt to retrieve a state value using the RelayState first before checking if IDP-initiated flow is allowed. * Only address the panic in IDP-initiated login (#1) This change undoes some of the changes made in 4908b26, to just address the panic for IDP-initiated logins. I'll file an issue in the `crewjam/saml` repo about the other issue blocking IDP-initiated logins, which is how to support relay states from the IDP.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: