Building a composite attribute from sets of attributes

[Etienne Dysli Metref]

On 07/08/2019 15.18, Rod Widdowson wrote:
> Absolutely not.  AttributeValues ordering within an Attribute is
> guaranteed, this is required to make templating make sense.  By
> extension this is why we have Null attribute value types.

I happily stand corrected then. :)

Coming back to my fake LDAP data

swissEduPersonUniqueID=1234 at uniA.example.org,ou=affiliations,...
  swissEduID: XXXX
  swissEduPersonUniqueID: 1234 at uniA.example.org
  swissEduIDAttributeProviderIdentifier: <uniA's IdP>
  swissEduPersonHomeOrganization: uniA.example.org
  swissEduPersonHomeOrganizationType: university

swissEduPersonUniqueID=5678 at uniB.example.org,ou=affiliations,...
  swissEduID: XXXX
  swissEduPersonUniqueID: 5678 at uniB.example.org
  swissEduIDAttributeProviderIdentifier: <uniB's IdP>
  swissEduPersonHomeOrganization: uniB.example.org
  swissEduPersonHomeOrganizationType: university

Given those two results, the output of the DataConnector will always be:

swissEduPersonUniqueID: 1234 at uniA.example.org, 5678 at uniB.example.org
swissEduIDAttributeProviderIdentifier: <uniA's IdP>, <uniB's IdP>
etc.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://shibboleth.net/pipermail/dev/attachments/20190807/76dac388/attachment.sig>