why is my SP using SOAP?!

[Kevin Foote]

On Jun 19, 2014, at 8:53 AM, Liam Hoekenga <liamr at umich.edu> wrote:

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

Is the SP getting all the attributes it wants from both your IdPs ?? 

If you have 8443 setup as an AA then SP will query back if it doesn’t get the attributes it wants. 

(I think this is what I recall seeing) 

--------
thanks
 kevin.foote