why is my SP using SOAP?!

[Liam Hoekenga]

I'm going a bit crazy here.

Our test SP is using SOAP for two of our non-prod IdPs (A, B), but normal
attribute push for the other non-prod IdP (C) and the prod IdP (D).

I had tested the SOAP connection last year, but had to use the long-form
version of shibboleth2.xml, updating the acsIndex element SessionInitiator
entry, and setting the SAML2/Artifact endpoint as the default.

I have since switched back to the short-form shibboleth2.xml, which doesn't
specify any of that.

While the metadata for the IdPs A and B do (currently) have the artifact
resolution and attribute service endpoints, that's true for IdPs C and D.

Why is it using soap for A and B?

Liam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20140619/90598ba7/attachment.html