why is my SP using SOAP?!

[Cantor, Scott]

On 6/19/14, 11:53 AM, "Liam Hoekenga" <liamr at umich.edu> wrote:
>
>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).

If you don't want the SP to ever use SOAP, you'd have to disable artifact
binding use, and comment out the Query AttributeResolver.

>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.

You don't need the long form to do that, but yes, getting artifacts to
actually get used can be somewhat tricky by design.

>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?

Probably because no attributes are being sent to it.

-- Scott