Versions Compared

Key

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


Tip
titleResearch and Scholarship Entity Category

The MyAccessID IAM Service supports the Research and Scholarship (R&S) Entity Category. As such, MyAccessID expects to receive the R&S attribute bundle from IdPs in eduGAIN supporting the R&S Entity Category.


Tip
titleCode of Conduct Entity Category

As a service that meets the requirements for and supports the entity category of Code of Conduct, the service specifically declares the attributes it requires.


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 AssuranceeduPersonAssuranceWill 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.


Depending on which protocol the IdP is using, SAML or OIDC, attributes need to be released in the following format, respectively.:

  • SAML Attribute Names

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
Subject ID
urn:oasis:names:tc:SAML:attribute:subject-idsubject-id
Pairwise ID
urn:oasis:names:tc:SAML:attribute:pairwise-idpairwise-id
Community Identifier
urn:oid:0.9.2342.19200300.100.1.3 email
urn:oid:1.3.6.1.4.1.25178.
4
1.
1
2.
6
9
voPersonIDEmail
schacHomeOrganization
urn:oid:
0
1.
9
3.
2342
6.
19200300
1.
100
4.1.
3 emailCommon Nameurn:oid:2.5.4.3cnGiven NamegivenNameFamily Nameurn:oid:2.5.4.4 surnameAffiliation
5923.1.1.1.6eduPersonPrincipalName

urn:oid:

2.5.4.42

1.3.6.1.4.1.5923.1.1.1.9

eduPersonScopedAffiliation

urn:oid:1.3.6.1.4.1.5923.1.1.1.
9
10

eduPersonTargetedID

urn:oid:1.3.6.1.4.1.5923.
25178
1.
4
1.1.11

eduPersonScopedAffiliation

voPersonExternalAffiliation

Home Organization
eduPersonAssurance
urn:oid:1.3.6.1.4.1.
25178
5923.1.1.
2
1.
9
13
schacHomeOrganizationAssurance
eduPersonUniqueId
urn:oid:1.3.6.1.4.1.5923.1.1.1.
11eduPersonAssurance

OIDC Claim Names

...

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 Claim
Subject ID
Scope
subject-id
Community Identifiervoperson_idEmail
openid
emailemail
Display Name
name
Given Name
profile
given_name
Family Name
profile
familty
family_name
Affiliation
profile
voperson_idaarc
eduperson_entitlementaarc

eduperson_scoped_affiliation

aarc
voperson_external_affiliation
Home Organization
aarc
eduperson_assuranceaarc
schac_home_organization
Assuranceeduperson_assurance