-
Notifications
You must be signed in to change notification settings - Fork 188
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
To implement SAML2 Artifact Resolution Profile #26
Comments
Hi @philiptran , After replying to you in #23, we had received more feedback about this profile. I've created a JIRA [1], so we can track all discussions and code from there. I've also created some branches:
We`ll probably need to work with both repositories. The first one contains the SAML core codebase, while the second is related with the integration with the different containers (bindings) where the SAML flow is actual implemented. You can reach me anytime on #picketlink at IRC Freenode or send me an e-mail ([email protected]), so we can start an initial discussion about this implementation and planning. Thanks. |
Maybe a good start would be artifact resolution for assertion responses. We can keep HTTP Redirect Binding/Profile for AuthnRequests and test the functionality only for assertion responses. I think that can be useful to deliver something fast and test overall design. Wdyt ? |
Hi Pedro, Thank you for the prompt response. I was thinking along that line also. Basically I am looking at Section 3.6 (HTTP Artifact Binding) of the SAML2 Bindings specs and Section 3.5 (Artifact Resolution Protocol) of the SAML2 Core specs. As I am currently busy with something else, I will find some time over the weekend to look at the JIRA as well as the branches to see what we have up to now before contacting you via email. Best Regards, |
Hi,
Refer to #23, I would like to contribute in the implementation of the HTTP Artifact Resolution Profile. Could you please provide some leads to get started? Thank you.
Best Regards,
Philip Tran
The text was updated successfully, but these errors were encountered: