You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

This document describes the SAML attributes and OIDC claims that are available to relying parties  connected to the MyAccessID Service. Attribute - claims marked as Mandatory will always be available to a relying party. Attribute - claims marked as Optional will be made available under certain circumstances. For example, some attributes - claims can be available only if the respective attributes - claims are released by the home Identity Provider of the user. Attributes - claims and values marked as Experimental might change or removed in the future, so relying parties should not rely on them, but use them only for experimental purposes.

List of Attributes - Claims

Community User Identifier

NameCommunity User Identifier
Description

User’s Community Identifier is an opaque and non-revocable identifier (i.e. it cannot change over time) that follows the syntax of eduPersonUniqueId  attribute of eduPerson.

It consists of “uniqueID” part and fixed scope “myaccessid.org”, separated by at sign. The uniqueID part contains up to 64 hexadecimal digits (a-f, 0-9)

SAML Attribute(s)

- 1.3.6.1.4.1.5923.1.1.1.13 (eduPersonUniqueId)

- urn:oasis:names:tc:SAML:attribute:subject-id

OIDC claim(s)sub (public)
OIDC claim locationThe claim is available in:

ID token
Userinfo endpoint
Introspection endpoint
OIDC scopeopenid
OriginMyAccessID assigns this attribute to a user when they register on the Service
ChangesNo
MultiplicitySingle-valued
AvailabilityMandatory
Example28c5353b8bb34984a8bd4169ba94c606@MyAccessID.org
Notes

eduPerson defines the comparison rule caseIgnoreMatch for eduPersonUniqueID. 

Relying services are encouraged to validate the scope of this attribute against the values permitted for MyAccessID. MyAccessID makes exclusive use of scope MyAccessID.org“. 

The MyAccessID identifier and username “test@MyAccessID.org” are test accounts reserved for testing and monitoring the proper functioning of the MyAccessID Login. The Relying parties should not authorise it to access any valuable resources.

Display Name

NameDisplay Name
Description

User’s name (firstname lastname).

SAML Attribute(s)

urn:oid:2.16.840.1.113730.3.1.241 (displayName)

OIDC claim(s)name
OIDC claim locationThe claim is available in:

 ID token
Userinfo endpoint
Introspection endpoint
OIDC scopeprofile
OriginEntered by the user when they register on MyAccessID
ChangesYes
MultiplicitySingle-valued
AvailabilityMandatory
ExampleJack Dougherty
Notes


Given Name

NameGiven Name
Description

Name strings that are the part of a person's name that is not their surname (see RFC4519).

SAML Attribute(s)

urn:oid:2.5.4.42 (givenName)

OIDC claim(s)given_name
OIDC claim locationThe claim is available in:

 ID token
Userinfo endpoint
Introspection endpoint
OIDC scopeprofile
OriginEntered by the user when they register on MyAccessID
ChangesYes
Multiplicity

Single-valued

AvailabilityMandatory
ExampleJack
Notes

In the specification of urn:oid:2.5.4.42 it is stated that the attribute supports multiple values, but the OIDC claim support only a single value. MyAccessID will release a single value to both SAML and OIDC relying parties

Family Name

NameFamily Name
DescriptionContains name strings for the family names of a person.
SAML Attribute(s)

urn:oid:2.5.4.4 (surname)

OIDC claim(s)family_name
OIDC claim locationThe claim is available in:

 ID token
Userinfo endpoint
Introspection endpoint
OIDC scopeprofile
OriginEntered by the user when they register on MyAccessID
ChangesYes
Multiplicity

Single-valued

AvailabilityMandatory
ExampleDougherty
Notes

In the specification of urn:oid:2.5.4.4 it is stated that the attribute supports multiple values, but the OIDC claim support only a single value. MyAccessID will release a single value to both SAML and OIDC relying parties

Email address

NameEmail address
Description

Email address of the user.

SAML Attribute(s)

urn:oid:0.9.2342.19200300.100.1.3 (email)

OIDC claim(s)email
OIDC claim locationThe claim is available in:

 ID token
Userinfo endpoint
Introspection endpoint
OIDC scopeemail
OriginEntered by the user when they register on MyAccessID. Users have to verify their e-mail address before they are registered on MyAccessID
ChangesYes
Multiplicity

Single-valued

AvailabilityMandatory
Examplejack.dougherty@example.com
Notes


Affiliation within Home Organization

NameAffiliation 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:

  • Faculty

    The person is a researcher or teacher in their home organisation. 

    The exact interpretation is left to the home organization, but the intention is that the primary focus of the person in their home organisation is in research and/or education. 

    Note. This attribute value is for users in the academic sector

  • Member

    Member is intended to include faculty, industry-researcher, staff, student and other persons with a full set of basic privileges that go with membership in the home organisation, as defined in eduPerson. 

    In contrast to faculty, among other things, this covers positions with managerial and service focus, such as service management or IT support.

  • Affiliate

    The affiliate value indicates that the holder has some definable affiliation to the home organisation NOT captured by any of faculty, industry-researcher, staff, student and/or member.

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.25178.4.1.11 (voPesonExternalAffiliation)

OIDC claim(s)voperson_external_affiliation
OIDC claim locationThe claim is available in:

 ID token
Userinfo endpoint
☐ Introspection endpoint
OIDC scopevoperson_external_affiliation
Origin

To become a holder of the faculty, industry-researcher or member attribute values in MyAccessID the user must have either 

  • Performed federated login to MyAccessID using their home organisation’s credentials, during which the home organisation releases the related eduPersonAffiliation or eduPersonScopedAffiliation attribute, or 
  • Be assigned that value manually in MyAccessID by a dedicated person in their home organisation 

To become a holder of the affiliate value, the user must either 

  • Use either of the two alternatives above, or
  • Demonstrate they control an e-mail address that belongs to the home organisation
ChangesYes
Multiplicity

Multi-valued

AvailabilityOptional
Examplefaculty@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.

MyAccessID asserts attribute values with different scopes. The Relying services are not supposed to do SAML scope check to this attribute.

Assurance

Name

Assurance

Description

Assurance of the identity of the user, following REFEDS Assurance Framework (RAF).

Following RAF values are qualified and automatically set for all MyAccessID identities:

  • https://refeds
  • https://refeds/ID/unique
  • https://refeds/ID/eppn-unique-no-reassign
  • https://refeds/IAP/low
  • https://refeds$/ATP/ePA-1m
  • https://refeds/ATP/ePA-1d

Following RAF values are set if the currently used authentication provider asserts (or otherwise qualifies to) them:

  • https://refeds/IAP/medium
  • https://refeds/IAP/high
SAML Attribute(s)

urn:oid:1.3.6.1.4.1.5923.1.1.1.11 (eduPersonAssurance)

OIDC claim(s)eduperson_assurance
OIDC claim locationThe claim is available in:

 ID token
Userinfo endpoint
☐ Introspection endpoint
OIDC scopeeduperson_assurance
Origin

MyAccessID is the origin for values it has set (see description).

The current authentication provider is the origin for the values it asserts (or otherwise qualifies to).

ChangesYes
Multiplicity

Multi-valued

AvailabilityMandatory
Example
  • https://refeds
  • https://refeds/ID/unique
  • https://refeds/ID/eppn-unique-no-reassign
  • https://refeds/IAP/low
  • https://refeds$/ATP/ePA-1m
  • https://refeds/ATP/ePA-1d
NotesThis attribute defines just the identity assurance. Authentication assurance is described using authentication contexts (SAML authentication context or OIDC acr claim).

MyAccessID Username

Name

MyAccessID Username

Description

The MyAccessID username is a user selected, human-readable, revocable identifier (i.e. the user can change it). It is intended to be used when a unique identifier needs to be displayed in the user interface (e.g. wikis or Unix accounts).

It has the syntax of eduPersonPrincipalName, which consists of “user” part and a fixed scope “MyAccessID.org”, separated by the @ sign. The user part (syntax derived from Linux accounts) begins with a lowercase letter or an underscore, followed by lower case letters, digits, underscores, or dashes and should between 4 and 16 characters long. The following regular expression applies: (^[a-z0-9_-]{4,16}$)

The usernames beginning with an underscore are dedicated to MyAccessID service IDs. (Experimental)

SAML Attribute(s)

urn:oid:1.3.6.1.4.1.5923.1.1.1.6 (eduPersonPrincipalName)

OIDC claim(s)eduperson_principal_name
OIDC claim locationThe claim is available in:

 ID token
Userinfo endpoint
☐ Introspection endpoint
OIDC scopeeduperson_principal_name
OriginSet when a user registers on MyAccessID
ChangesYes
Multiplicity

Single-valued

AvailabilityMandatory
Example

dougherty@MyAccessID.org

Notes

Revoked identifiers will not be reassigned.

Relying services are encouraged to validate the scope of this attribute against the values permitted for MyAccessID. MyAccessID will make exclusive use of scope “MyAccessID.org”. 

The MyAccessID identifier and MyAccessID username “test@MyAccessID.org are test accounts reserved for testing and monitoring the proper functioning of the MyAccessID Login. The Relying parties should not authorise it to access any valuable resources.

SSH Public Key

Name

SSH Public Key 

DescriptionSSH public key of the user
SAML Attribute(s)

urn:oid:1.3.6.1.4.1.24552.500.1.1.1.13 (sshPublicKey)

OIDC claim(s)ssh_public_key
OIDC claim locationThe claim is available in:

 ID token
Userinfo endpoint
☐ Introspection endpoint
OIDC scopessh_public_key
OriginCreated and uploaded to MyAccessID by the user.
ChangesYes
Multiplicity

Multi-valued

AvailabilityOptional
Example

ssh-ed25519 AAAAC3NqaC1lZDI1TTE5AAAAIJ4pfKk7hRdUVeMfrKdLYhxdKy92nVPuHDlVVvZMyqeP

Notes
  • No labels