<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">A vendor’s SAML code is rejecting the SAML assertion from our Shibboleth IdP.<div>They have requested I change the SAML assertion so that all attributes be encoded with a attrname-format of “basic” </div><div>rather than the Shibboleth default of “uri”.</div><div><br></div><div>Looking at <a href="https://wiki.shibboleth.net/confluence/display/SHIB2/SAML2XMLObjectAttributeEncoder">https://wiki.shibboleth.net/confluence/display/SHIB2/SAML2XMLObjectAttributeEncoder</a></div><div>it looks as though I could define variant attributes by adding the optional element</div><div>nameFormat=“...:basic” in the AttributeEncoder. If that’s roughly right, do I include the entire desired SAML string, </div><div>nameFormat=“urn:oasis:names:tc:SAML:2.0:attrname-format:basic” </div><div>in the AttributeEncoder?</div><div><br></div><div><br></div><div>David Bantz</div><div>U Alaska</div><div><br></div><div><br></div></body></html>