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

Compare with Current View Page History

« Previous Version 21 Next »

When you connect to SURFconext you can use several standards to connect. Different standards result in different protocols and in their turn tend to use a jargon specific to that standard. It will probably not surprise you that this is the case with OpenID Connect. This page depicts how to translate SAML attributes to OpenID Connect claims.

OpenID Connect Claims and SAML attributes

Most services require extra information about the authenticated user, such as name, email address or affiliation. In OpenID Connect (OIDC), this extra information comes in the form of claims, whereas in SAML, claims are called attributes. In SURFconext, the user authenticates at his Identity Provider (called OpenID Provider in OIDC) - this all happens using SAML. SURFconext translates the incoming SAML attributes to OIDC claims and provides them at the userinfo endpoint for your Service Provider (called Relying Party in OIDC) to consume.

Please note: SURFconext only caches the claims at the userinfo endpoint for a limited amount of time: 1 hour (after a successful authentication). If you request claims at the userinfo endpoint after this, the user is required to re-authenticate.

An extensive list of SAML attributes together with their details and properties can be fond on our support page about attributes.  Those SAML attributes are provided by institutions connected to SURFconext as Identity Provider. You can use any of those attributes in your service (SURFconext translates them to OpenID Connect claims), however you must comply with our data minimisation policy, meaning you are only allowed to receive the bare minimum of attributes strictly needed for you to operate your service.

The following table describes the translation from SAML attributes to OIDC claims:


OIDC claimSAML AttributeDescription of SAML attribute
sub
OpenID Subject (not available as SAML attribute)
given_nameurn:mace:dir:attribute-def:givenNameGivenname attribute
family_nameurn:mace:dir:attribute-def:snSurname attribute
nameurn:mace:dir:attribute-def:cnCommon name attribute
nicknameurn:mace:dir:attribute-def:displayNameDisplay name attribute
preferred_username
urn:mace:dir:attribute-def:displayNameDisplay name attribute
localeurn:mace:dir:attribute-def:preferredLanguagePreferred language attribute
emailurn:mace:dir:attribute-def:mailEmail address attribute
schac_home_organizationurn:mace:terena.org:attribute-def:schacHomeOrganizationOrganization attribute
schac_home_organization_typeurn:mace:terena.org:attribute-def:schacHomeOrganizationTypeOrganization type attribute
edu_person_affiliationsurn:mace:dir:attribute-def:eduPersonAffiliationAffiliation attribute
edu_person_scoped_affiliations
urn:mace:dir:attribute-def:eduPersonScopedAffiliationScoped affiliation attribute
edu_person_targeted_id
urn:mace:dir:attribute-def:eduPersonTargetedIDeduPersonTargetedID
uidsurn:mace:dir:attribute-def:uidUid attribute
schac_personal_unique_codesurn:schac:attribute-def:schacPersonalUniqueCodePersonal code attribute
edu_person_principal_name
urn:mace:dir:attribute-def:eduPersonPrincipalNameEduPersonPrincipleName
edu_person_entitlementsurn:mace:dir:attribute-def:eduPersonEntitlementeduPersonEntitlement
  • No labels