Closed tmilos closed 10 years ago
Main logic from building the AuthnRequest including the AssertionConsumerServiceURL and ProtocolBinding attributes is in https://github.com/aerialship/lightsaml and will be resolved with aerialship/lightsaml#20
After that in this project the spMeta configuration has to be adjusted for eventual new fields, and finally functionally tested
Also related to #17 ACS must receive Response only on POST
Intro
Windows azure has following IDP metadata
Redirect binding spMeta config
If in security.yml is setup as
Then redirect binding is used to send AuthRequest with attribute ProtocolBinding="HTTP-POST", and Azure responds with
POST binding spMeta config
If in security.yml is setup as
Then post bindind is used to send AuthRequest with attribute ProtocolBinding="HTTP-Redirect", and Azure responds with HTTP 404 Page not found.
Summary
saml-core-2.0-os.pdf states AuthRequest ProtocolBinding attribute references "binding to be used when returning the message" while in current implementation it's both the binding that will be used for sending and as the value of that attribute.
It should be possible to use one binding for sending AuthRequest message that's different then the one put in it's ProtocolBinding attribute