...
Name | Affiliation within Home Organization |
---|---|
Description | One or more home organisations (such as, universities, research institutions or private companies) this user is affiliated with. The syntax and semantics follows eduPersonScopedAffiliation attribute. Following values are recommended for use to the left of the “@” sign:
If a person has faculty or industry-researcher affiliation with a certain organisation, they have also the member affiliation. However, that does not apply in a reverse order. Furthermore, those persons who do not qualify to member have an affiliation of affiliate. |
SAML Attribute(s) | urn:oid:1.3.6.1.4.1.34998.3.3.1.11 (Experimental) |
OIDC claim(s) | voperson_external_affiliation |
OIDC claim location | The claim is available in: ☐ ID token ☑ Userinfo endpoint ☐ Introspection endpoint |
OIDC scope | voperson_external_affiliation |
Origin | To become a holder of the faculty, industry-researcher or member attribute values in eduTEAMS the user must have either
To become a holder of the affiliate value, the user must either
|
Changes | Yes |
Multiplicity | Multi-valued |
Availability | Optional |
Example | faculty@helsinki.fi industry-researcher@zeiss.com member@ebi.ac.uk |
Notes | The freshness of the attribute values is managed by asking users to refresh the value every 12 months using the procedure described above. eduTEAMS asserts attribute values with different scopes. The Relying services are not supposed to do SAML scope check to this attribute. |
...