Multiple Attribute Elements

[Peter Schober]

* Stephen McIntyre <openamstudent at gmail.com> [2015-01-26 19:50]:
>         <resolver:AttributeEncoder xsi:type="enc:SAML1String"
> name="urn:mace:dir:attribute-def:myUID" />

Also note that you can't just make up attribute names in someone
else's namespace (MACE-Dir's legacy namespace, in this case). I know
this is meant to be an example but it's a bad one as such.
Since you claim to care about friendlyName I doubt the SP in question
speaks SAML1, in which case just don't define an encoder for SAML1.

> 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?

Not, they're seperate AttributeDefinitions to the IDP. But it hints at
an SP that's violating the SAML spec by looking at the friendlyName
instead of Name + NameFormat.
-peter