An open discussion list for topics related to the eduGAIN interfederation service.

[Jaime Pérez Crespo <jaime.perez AT uninett.no>]

On 29 Oct 2014, at 16:26 pm, Peter Schober <peter.schober AT univie.ac.at> wrote:
> I'm happy as the next person to see a rich attribute ecosystem emerge,
> but so far I feel the only somewhat interoperable and
> can-be-assumed-to-exist attributes in interfederation use (i.e., not
> your locally defined attributes within a single closed community or
> federation) are the ones I mentioned here[1]:
> 
> Name attributes
>  displayName (urn:oid:2.16.840.1.113730.3.1.241)
>  givenName (urn:oid:2.5.4.42)
>  sn/surname (urn:oid:2.5.4.4)
> Identifiers
>  eduPersonTargetedID (a.k.a. SAML2 persistent NameID, 
> urn:oid:1.3.6.1.4.1.5923.1.1.1.10)
>  eduPersonPrincipalName (urn:oid:1.3.6.1.4.1.5923.1.1.1.6)
>  mail (urn:oid:0.9.2342.19200300.100.1.3)
> Authorization
>  eduPersonScopedAffiliation (urn:oid:1.3.6.1.4.1.5923.1.1.1.9)
>  eduPersonEntitlement (urn:oid:1.3.6.1.4.1.5923.1.1.1.7)
> Organizational data
>  schacHomeOrganization (urn:oid:1.3.6.1.4.1.25178.1.2.9)

This is a good example. You definitely cannot expect schacHomeOrganization to 
exist if you are talking to Feide. Same applies to 
eduPersonScopedAffiliation, for instance.

--
Jaime Pérez
UNINETT / Feide
mail: jaime.perez AT uninett.no
xmpp: jaime AT jabber.uninett.no

"Two roads diverged in a wood, and I, I took the one less traveled by, and 
that has made all the difference."
- Robert Frost