SP using SAML 1 AttributeService instead of SAML2 HTTP POST

[Gloeb, Geoff]

I was running through the transaction logs on our SP (v2.5.3) and see they are almost all "using (Protocol: urn:oasis:names:tc:SAML:1.1:protocol)”.  Even our own IdP is using SAML 1.1. I removed the line AttributeService Binding="urn:oasis:names:tc:SAML:1.0:bindings:SOAP-binding” from the idp-metadata on our dev IdP and tested.  Now the log shows SAML 2.0.  What would make the SP use the SAML 1 AttributeService instead of just using a SAML 2 POST? Our SP metadata AssertionConsumerService SAML 2.0 HTTP-POST is index=1.  Appreciate the help.

Thanks

Geoff



The information in this e-mail may be privileged and confidential, intended only for the use of the addressee(s) above. Any unauthorized use or disclosure of this information is prohibited. If you have received this e-mail by mistake, please delete it and immediately contact the sender.