Multiple Attribute Elements

[Stephen McIntyre]

Quick question -

On the Shibboleth wiki () I read "Defining more than one attribute encoder
allows a deployer to transform a single attribute into multiple <Attribute>
elements with different names, name formats, or friendly names.". I've done
this for some attributes, but I'm wondering about a situation like the
following attribute definitions:

    <resolver:AttributeDefinition xsi:type="ad:Simple" id="myUID"
sourceAttributeID="myName">
        <resolver:Dependency ref="myLDAP" />
        <resolver:AttributeEncoder xsi:type="enc:SAML1String"
name="urn:mace:dir:attribute-def:myUID" />
        <resolver:AttributeEncoder xsi:type="enc:SAML2String"
name="urn:oid:1.3.6.1.4.1.5923.1.1.1.6" friendlyName="myUID" />
    </resolver:AttributeDefinition>

    <resolver:AttributeDefinition xsi:type="ad:Simple" id="myUserName"
sourceAttributeID="myName">
        <resolver:Dependency ref="myLDAP" />
        <resolver:AttributeEncoder xsi:type="enc:SAML1String"
name="urn:mace:dir:attribute-def:myUserName" />
        <resolver:AttributeEncoder xsi:type="enc:SAML2String"
name="urn:oid:1.3.6.1.4.1.5923.1.1.1.6" friendlyName="myUserName" />
    </resolver:AttributeDefinition>

My plan is to send myUID to one entity (it's this way for historical
purposes) and myUserName to a different entity. However, besides sharing
the same sourceAttributeID, they also share the same name (i.e.
'urn:oid:1.3.6.1.4.1.5923.1.1.1.6', just a throw-away example), though
their friendlyNames are different. Will this pose problems for the
Shibboleth IDP I define this in?

Eventually I will get rid of the historical definition, but I want to go
one step at a time, and wanted to make sure this was possible before
implementing it.

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20150126/ea6689e4/attachment.html