multiple AttributeEncoders of the same type in an AttributeDefinition?

[Christopher Bongaarts]

On 9/11/2013 2:46 PM, Liam Hoekenga wrote:
> Is it legal to have multiple AttributeEncoders of the same type in a 
> single AttributeDefinition?
>
> We're dealing with a vendor who expects
>
>  <resolver:AttributeEncoder xsi:type="enc:SAML2String" name="email" 
> friendlyName="mail" />
>
> instead of ..
>
> <resolver:AttributeEncoder xsi:type="enc:SAML2String" 
> name="urn:oid:0.9.2342.19200300.100.1.3" friendlyName="mail" />
>
> Having two SAML2String encoders in the definition /seems/ to work, so 
> I'm mostly wondering if it's *supposed* to work.
>

I usually work around these by defining a second attribute based on the 
first with the alternate encoder, so it can be released independently.

-- 
%%  Christopher A. Bongaarts   %%  cab at umn.edu          %%
%%  OIT - Identity Management  %%  http://umn.edu/~cab  %%
%%  University of Minnesota    %%  +1 (612) 625-1809    %%

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130911/94d9c1e2/attachment.html