AssertionConsumerService and ProtocolBinding are mutually exclusive as per Saml 2 specification
Our Customer updated his IDP and now our software ist not working anymore.
The problem is, our request includes AssertionConsumerServiceIndex and ProtocolBinding Parameter.
This seems not be allowed in saml specification.
Is it possible to suppress the AssertionConsumerServiceIndex, because we need the protocolBinding.
Thanks and Regards
asked 3/6/2023 6:46:22 PM
add a comment
Hi,
just to complete the question. I found the solution myself.
The secret ist just not to set the AssertionConsumerServiceIndex. Then it is not in the request.
Thanks
Theo
answered 3/21/2023 9:34:20 AM
Hi Theo,
Here is the link [Gets or sets the location to which the Response message should be returned to the requester.][1]To manage AssertionConsumerServiceIndex.
Thanks
[1]: https://doc.componentpro.com/ComponentPro-Saml/ComponentPro-Saml2-AuthnRequest-AssertionConsumerServiceIndex
answered 3/9/2023 7:43:49 AM
| Hi Martin, thanks for your reply. This is an integer. I can set it only to an integer value. But i need to supress it completly in the request. May be i can supress the protocolbinding by setting it to a blank string. This 2 parameters are mutually explusive. You can find that in saml2.0 specification. Thanks Theo Theo 3/12/2023 9:10:57 PM |