The services requires to uniquely identify users for authorization purposes. Without some a unique identifier, it is impossible to distinguish two different users between each other.

As a service that meets the requirements for and supports the entity category of R&S, the MyAccessID IAM Service is expected to receive the R&S attribute bundle, which includes a user identifier.

As a service that meets the requirements for and supports the entity category of Code of Conduct, the MyAccessID IAM Service specifically declares the attributes required to use the service.

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

pairwise-id

eduPersonPrincipalName1

eduPersonTargetedID

eduPersonUniqueId

Level of Assurance information will become mandatory in 2022

Access to services connected to PUHURI is allowed only with use of identities that fulfill certain identity assurance criteria.

To express the required assurance levels, the REFEDS Assurance suite https://wiki.refeds.org/display/ASS is used.

Requirements are defined for two aspects of identity assurance:

• Identifier uniqueness to ensure unambiguous identification of users;
• Identity proofing and credential issuance, renewal, and replacement to ensure that identity trustworthy represents right natural person.

Level of assurance for an identity issued to a user is expressed at the time of user authentication by the IdP sending eduPersonAssurance attribute with following values:

• https://refeds.org/assurance/ID/UNIQUE; or https://refeds.org/assurance/ID/eppn-unique-no-reassign, and
• https://refeds.org/assurance/IAP/medium or https://refeds.org/assurance/IAP/high

cn

The service requires to uniquely and persistently identify the users who are members of virtual teams as they will be assigned membership roles and access rights to teams resources. When applying for membership to a team or a project, the manager needs to be able to recognise the applicant and the team services used for the collaboration, expect to provide personalised access.

As a service that meets the requirements for and supports the entity category of R&S, it is expected to receive the R&S attribute bundle, which includes cn, displayName, sn and givenName.

As a service that meets the requirements for and supports the entity category of Code of Conduct, the service specifically declares the attributes required to use the service

sn + givenName

mail

The service needs to be able to contact the user regarding the status of their account.

As a service that meets the requirements for and supports the entity category of R&S, it is expected to receive the R&S attribute bundle, which includes the mail.

As a service that meets the requirements for and supports the entity category of Code of Conduct, it specifically declares the attributes required to use the service. As a service that supports Sirtfi, it is required that it is able to contact users.

eduPersonScopedAffiliation

Access to many of the HPC resources connected through MyAccessID in the context of EuroHPC (and beyond) relies on authorising users based on the affiliation of their members in their home organisation.

As a service that meets the requirements for and supports the entity category of R&S, it is expected to receive the R&S attribute bundle, which includes the eduPersonScopedAffiliation.

As a service that meets the requirements for and supports the entity category of Code of Conduct, the service specifically declares the attributes required to use the service

Access to many of the HPC resources connected through MyAccessID in the context of EuroHPC (and beyond) relies on authorising users based on their home organisation.

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