Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Attribute TypeAttributeRequirementExplanation
User Identifier

subject-id

Mandatory (at least one)

MyAccessID and the services connected through MyAccessID require to uniquely identify users. Without a unique identifier, it is not possible to distinguish two different users between each other.

As a service that supports Sirtfi, it is required that it is able to uniquely identify users.

1 The eduPersonPrincipalName can be used only if one of the following conditions are met:

i) the IdP supports the R&S Enitity Category,

ii) the eduPersonAssurance attribute is also released and it has a value of https://refeds.org/assurance/ID/eppn-unique-no-reassign,

iii) the federation in which the IdP has registered has a policy that prohibits the reassignment of the value of the eduPersonPrincipalName attribute

pairwise-id

eduPersonPrincipalName1

eduPersonTargetedID

eduPersonUniqueId

Level of AssuranceeduPersonAssuranceMandatory (starting March 1st 2023Will become mandatory (date TBD)

Access to the services connected through MyAccessID will be dominantly supported by identities coming from the IdPs from the R&E sector and eduGAIN.

See Level of Assurance Requirements for more information.


Name

cn

Mandatory  (at least one)

MyAccessID and the services connected through MyAccessID expect to receive the name of the user.

For example, when a user applies for a new project or for membership membership to an existing project, the managers need to be able to recognise who the applicant is.

displayName


sn + givenName

Mail

mail

Mandatory

MyAccessID needs to be able to contact the user regarding the status of their account. In addition, many of the services connected through MyAccessID expect the email of the user in order to be able contact the user about service related matters.

Affiliation

eduPersonScopedAffiliation

Mandatory

Access to many of the services connected through MyAccessID relies on authorising their member users based on affiliation with their home organisation.

OrganizationschacHomeOrganizationOptional

Access to many of the services connected through MyAccessID relies on authorising users based on their home organisation.

...

SAML Attributes MUST be sent using urn:oasis:names:tc:SAML:2.0:attrname-format:uri NameFormat. Below is the list of the canonical names of the SAML attributes:

SAML Attribute NameSAML Attribute Friendly Name
urn:oasis:names:tc:SAML:attribute:subject-idsubject-id
urn:oasis:names:tc:SAML:attribute:pairwise-idpairwise-id
urn:oid:0.9.2342.19200300.100.1.3 email
urn:oid:1.3.6.1.4.1.25178.1.2.9schacHomeOrganization
urn:oid:1.3.6.1.4.1.5923.1.1.1.6eduPersonPrincipalName

urn:oid:1.3.6.1.4.1.5923.1.1.1.9

eduPersonScopedAffiliation

urn:oid:1.3.6.1.4.1.5923.1.1.1.10

eduPersonTargetedID

urn:oid:1.3.6.1.4.1.5923.1.1.1.11eduPersonAssurance
urn:oid:1.3.6.1.4.1.5923.1.1.1.13eduPersonUniqueId
urn:oid:1.3.6.1.4.1.5923.1.1.1.16
eduPersonOrcid
urn:oid:2.5.4.3cn
urn:oid:2.5.4.4 surname
urn:oid:2.5.4.42givenName


  • OIDC Claims and Scopes
OIDC ClaimScope
subject-idopenid
emailemail
nameprofile
given_nameprofile
family_nameprofile
voperson_idaarc
eduperson_entitlementaarc

eduperson_scoped_affiliation

aarc
voperson_external_affiliationaarc
eduperson_assuranceaarc
schac_home_organization

...