non-default NameFormat in SAML assertion

David Bantz dabantz at alaska.edu
Fri Nov 22 20:16:32 EST 2013


A vendor’s SAML code is rejecting the SAML assertion from our Shibboleth IdP.
They have requested I change the SAML assertion so that all attributes be encoded with a attrname-format of “basic” 
rather than the Shibboleth default of “uri”.

Looking at https://wiki.shibboleth.net/confluence/display/SHIB2/SAML2XMLObjectAttributeEncoder
it looks as though I could define variant attributes by adding the optional element
nameFormat=“...:basic” in the AttributeEncoder.  If that’s roughly right, do I include the entire desired SAML string, 
nameFormat=“urn:oasis:names:tc:SAML:2.0:attrname-format:basic” 
in the AttributeEncoder?


David Bantz
U Alaska


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20131122/0ee8fde2/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://shibboleth.net/pipermail/users/attachments/20131122/0ee8fde2/attachment.bin 


More information about the users mailing list