Versions Compared

Old Version 1

changes.mady.by.user Tomasz Kuczyński

Saved on

compared with

New Version 2

changes.mady.by.user Tomasz Kuczyński

Saved on

Key

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

...

Tip
titleResearch and Scholarship Entity Category

The MyAccessID IAM GEANT AAI Service supports the Research and Scholarship (R&S) Entity Category. As such, MyAccessID expects GEANT AAI Service 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.


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.MyAccessID MyAccessID MyAccessID MyAccessID
Attribute TypeAttributeRequirementExplanation
User Identifier

subject-id

Mandatory (at least one)

MyAccessID and GEANT AAI Service and the services connected through MyAccessID GEANT AAI Service 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)


Name

cn

Mandatory  (at least one)

MyAccessID GEANT AAI Service and the services connected through MyAccessID GEANT AAI Service 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

GEANT AAI Service needs to be able to contact the user regarding the status of their account. In addition, many of the services connected through

GEANT AAI Service 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

GEANT AAI Service relies on authorising their member users based on affiliation with their home organisation.

OrganizationschacHomeOrganizationOptional

Access to many of the services connected through

GEANT AAI Service 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:

...