<div dir="ltr">Yes, SAML2. For some time I could not understand why the vendor insisted they received no attributes in my SAML, when my outgoing SAML assertion (POST) clearly contained them. They were not forthcomming, just repeating that they received no attributes; I finally realized they disregard the attributes, just consuming the authN portion, then use SOAP/AttributeQuery to ask for attributes. I can't explain why they don't consume the attributes in the first SAML response; I suppose it might reflect sequential and/or independent deployment of the two uses of SAML.</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 9, 2015 at 12:39 PM, Tom Scavo <span dir="ltr"><<a href="mailto:trscavo@gmail.com" target="_blank">trscavo@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mon, Feb 9, 2015 at 2:39 PM, IAM David Bantz <<a href="mailto:dabantz@alaska.edu">dabantz@alaska.edu</a>> wrote:<br>
><br>
> This is the first and only attribute query I've encountered; is there an<br>
> obvious way to configure the IdP to successfully return attributes?<br>
<br>
</span>David, is this SAML2? Are you pushing attributes on the front channel?<br>
If so, why does the vendor need to query?<br>
<span class="HOEnZb"><font color="#888888"><br>
Tom<br>
</font></span><div class="HOEnZb"><div class="h5">--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br>
</div></div></blockquote></div><br></div>