<div dir="ltr">I'm going a bit crazy here.<div><br></div><div>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).</div><div><br>
</div><div>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.</div>
<div><br></div><div>I have since switched back to the short-form shibboleth2.xml, which doesn't specify any of that.</div><div><br></div><div>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.</div>
<div><br></div><div>Why is it using soap for A and B?</div><div><br></div><div>Liam</div></div>