non-default NameFormat in SAML assertion

[Nate Klingenstein]

David,

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?

Yes, roughly.  I'd make copies of any attributes the vendor expects to receive in that namespace specific to that vendor with their own attribute ID(and so modified encoders).  Then, release the modified attributes to this vendor without impacting your other integrations.

The usual caveats here apply regarding loose interpretation of the SAML specifications and the resulting increase in configuration complexity for you and those who follow.  It would be great if this vendor could handle attributes of URI form defined as, well, URI's.

Have a good weekend,
Nate.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20131123/21dc2aed/attachment.html