This page will list all the SAML2 attributes that SURFconext and their Identity Providers have to offer. An attribute is a characteristic that describes a user. It is a 'name:value' pair. The attributes included in the SAML assertion correspond to certain attributes a service provider needs to work properly. In general they are needed to:
- Convey user information from the Identity provider or IdP to the service provider
- Create an account for the user at the service provider
- Authorize specific services at the service provider
Now, when a user logs in to a Service Provider, SURFconext sends a SAML assertion to the Service Provider via the browser of the user, that contains a:
- User identifier. Al services receive these and are either a configurable Transient or Persistent NameID.
and Additional attributes. These are optional and differ per Service.
When a user logs in to a service provider, SURFconext sends a so-called SAML assertion to the service provider. This SAML assertion contains a number of statements about the user who is logging in to you service, including his identity, and possibly a number of additional attributes (see below). More information about SAML can be found on this page.
...
Note |
---|
SURFconext's SAML2 implementation adheres to the SAML2int standard |
...
0.2.1. The header on the link above states that work on saml2int has moved to Kantara Initiative. Until further notice, the SAML2int standard SURFconext adheres to remains at 0.2.1. |
Info |
---|
Before you start digging into the theoretical stuff on this page, you might want to start with our 'best practice' page for an introduction to and how attributes are best used. |
Table of Contents |
---|
User identifiers
The user'
On this page, we explain which attributes SURFconext and its identity providers can provide for the services. A guide for identity providers, explaining which attributes should be released to SURFconext, is found elsewhere.
User identifiers
The user's identity is transmitted in the form of the NameId NameID element of the SAML statement. SPs should use the NameId (rather than email address, or other attributes that might change over time) to identify users. The NameId . Every IdP must supply a NameID, but for privacy reasons SURFconext will generate a new one, which is duplicated in the attribute eduPersonTargetedID.
To identify a user the Service Provider must use the NameID or eduPersonTargetedID. The NameID is guaranteed to be stable and never change for a fixed user (, except in the case of transient identifiers, see below).
SURFconext can provide NameIds of three different types:
. SURFconext will generate a NameID for each new user. It is unique for the user and specific to the SP, so SP's cannot correlate their received NameID's between each other. There are two types of NameIDs:
urn:oasis:names:tc:SAML:2.0:nameid-format:persistent
A persistent NameID contains a unique string identifying A persistent identifier. A persistent NameId contains a random string that uniquely identifies the user for this SP , and which persists is persisting over multiple sessions for the same user..urn:oasis:names:tc:SAML:2.0:nameid-format:transient
A transient NameID contains a unique string identifying A transient identifier. A transient NameId contain a random string that uniquely identifies the user for this SP during the session. Once If the user 's session at SURFconext expires and the users logs into your service once morelogs in again, a new transient identifier will be generated for the user and SP.- A legacy identifier. A legacy NameId contains a human-readable identifier of the form
urn:collab:person:example.com:johndoe
. This form of the identifier is deprecated and is not available for newly connected services. The reason for this is that SURFconext wants to have fine-grained control over the released attributes. This is easier to manage if no personal information is disclosed in the NameId identifier. If the SP needs information that is contained in the legacy NameId format (for example, the user's home institution), they should use proper attributes (for example, schacHomeOrganisation, see below) as a source for this information.
Persistent and transient identifiers typically have the form "bd09168cf0c2e675b2def0ade6f50b7d4bb4aaef
". However, this form may change in the future, and service providers MUST NOT rely on the fact that the NameId is a 40-character hexadecimal string.
The two supported NameId types, for respectively persistent and transient NameId
specifiers, are
urn:oasis:names:tc:SAML:2.0:nameid-format:persistent
urn:oasis:names:tc:SAML:2.0:nameid-format:transient
which are specified in sections 8.3.7 and 8.3.8 of the SAML2 core specification.
The legacy format has the type urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified
, as defined in the SAML 1.1 specification. Legacy identifiers in SURFconext have the form uid@example.org
. Although these might look like email addresses, they are not, and mail sent to such addresses might not (and mostly will not) be delivered.
By default, SURFconext offers the transient form of the NameId to services. Service providers who have a need for persistent identifiers can negotiate use of the persistent NameId format when their service is connected to SURFconext.
Attributes
By default, the NameId is the only piece of information about the euthenticated user that SURFconext conveys to SPs. However, in many cases these services require more information about the user, such as a name or an email address.
Because of European privacy regulations, we cannot release such information to the SPs by default. In order to receive additional information, the user's home institution needs to give permission for each SP to receive its users' data. Typically, such permission will be arranged for during the initial SURFconext setup procedure.
Furthermore, when a user first logs in to a service, SURFconext informs them about the attributes and the information contained therein that is going to be sent to the service. If the user does not consent to his information being transmitted, they can still abort the login to the service.
SURFconext supports two atttributes schemas: the urn:oid
schema and the urn:mace
schema. Both of these can be used to convey the same information (except for the NameId, which is only available in the urn:oid
schema. By default SURFconext will provide attributes in both schemata as part of the assertion. It is not recommended to mix the use of these schemata.
Attribute overview
SURFconext supported relaying of the following attributes:
- .
Warning | ||
---|---|---|
| ||
The NameID and eduPersonTargetedID, which is basically a copy of the NameID, is unlikely to change and very privacy aware but can change when service providers or identity provider make critical changes. This can cause user profiles for services to be lost. The NameID, as used in the SAML assertion to a service provider when loggin' on, is generated using the uid, schacHomeOrganization, the Entity ID of the service provider together with a secret that uses a SHA algorithm. Institutions or services that are in production and change one of these attributes, will cause a new NameID and eduPersonTargetedID to be generated by SURFconext when doing so. This can cause loss of access to profiles at services. We will notify identity providers and service providers when we see a change in one of these attributes to prevent user data being lost. |
Changing attributes
As an Identity Provider it is important to realize that changing attributes in production on SURFconext in any way can have an impact on services users have access to. Attributes that you offer to SURFconext are used to create profiles, and data is often linked to them. Changing an attribute in any way can have unwanted results like users that are no longer able to access their valuable data. An example could be to modify the way you fill the email address (amongst others). For example: changing 'student.123456@university.nl' to 'john.doe@university.nl'. Do you plan to do this or do you start a project where this is the case? Contact us and send an email to support@surfconext.nl.
Useful links
- Table with attributes we recommend our institutions to release: https://wiki.surfnet.nl/display/surfconextdev/Vereiste+attributen
- Profile Page https://profile.surfconext.nl/ , showing what attributes are released by your IdP to SURFconext
- For new IdP's or for IdP's that upgrade their environment: system administrators will at some point be asked to share the metadata of their account for analyses. When asked, visit this page and click the 'Mail to SURFconext' button. We will get back to you when we have judged the submitted metadata.This page will also show you the attributes shared and their values.
Attribute schemas
A schema is an abstract representation of an object's characteristics and relationship to other objects.
SURFconext supports two attribute schemas:
urn:oid
schema (SAML2.0 compliant)urn
schema (SAML1.1 compliant)
Both can be used to convey the same information (except for the NameID, which is only available in the urn:oid
schema). By default SURFconext will provide attributes in both schemas as part of the assertion. However it is not recommended to mix the use of the schemas.
Attribute overview
SURFconext supports relaying of the following attributes:
Friendly name
Attribute name
Definition
Data type
Example
ID
Friendly name | Attribute name | Example |
---|---|---|
SAML NameID element | bd09168cf0c2e675b2def0ade6f50b7d4bb4aae | |
urn:mace:dir:attribute-def:sn | Doe Vermeegen | |
givenName |
2. |
5. |
UTF8 string
(unbounded)
bd09168cf0c2e675b2def0ade6f50b7d4bb4aae
Surname
4.42 | John Mërgim Lukáš Þrúður |
cn |
UTF8 string
(unbounded)
Vermeegen
?
3 | John Doe Prof.dr. Mërgim Lukáš Vermeegen 加来 千代, PhD. |
displayName |
840. |
1. |
UTF8 string
(unbounded)
Mërgim Lukáš
??
Common name
UTF8 String
(unbounded)
113730.3.1.241 | Dr. John Doe Prof.dr. Mërgim |
L. Vermeegen |
加来 千代, PhD. |
mail |
0. |
9. |
2342. |
19200300. |
100.1. |
3 | m. |
l. |
vermeegen@university. |
Email address
example. |
UTF8 String
(unbounded)
Prof.dr. Mërgim L. Vermeegen
? ??, PhD.
org maarten.'t.hart@uniharderwijk.nl "very.unusual.@.but valid.nonetheless"@example.com mlv@[IPv6:2001:db8::1234:4321] | |
urn:mace:terena.org:attribute-def:schacHomeOrganization |
|
1. |
3. |
6. |
1. |
4.1. |
RFC-5322 address
(max 256 chars)
m.l.vermeegen@university.example.org
"very.unusual.@.unusual.com"@example.com
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="b35f4d14-4ec1-4fa9-9a10-222602c52e15"><ac:plain-text-body><![CDATA[mlv@[IPv6:2001:db8::1234:4321]
]]></ac:plain-text-body></ac:structured-macro>
Organization
25178.1.2.9 | example.nl something.example.org | |
urn:mace:terena.org:attribute-def:schacHomeOrganizationType | urn:mace:terena.org:schac:homeOrganizationType:int:university |
urn:mace:terena.org:schac:homeOrganizationType:es:opi | |
Employee/student number | urn:schac:attribute-def: |
schacPersonalUniqueCode |
RFC-1035 domain string
university.example.org
14 | urn:schac:personalUniqueCode:nl:local:example.edu:employeeid:x12-3456 urn:schac:personalUniqueCode:nl:local:example.nl:studentid:s1234567 |
eduPersonAffiliation |
1.1. |
1. |
RFC-2141 URN
see Schac standard
urn:mace:terena.org:schac:homeOrganizationType:int:university
urn:mace:terena.org:schac:homeOrganizationType:es:opi
Affiliation
1 | employee, student, faculty, member, affiliate, pre-student |
Scoped affiliation | urn:mace:dir:attribute-def: |
eduPersonScopedAffiliation urn:oid:1.3.6.1.4.1.5923.1.1.1. |
Enum type (UTF8 String)
faculty, student, staff, (alum, member, affiliate, employee, library-walk-in)
Entitlement
9 | student@uniharderwijk.nl employee@uniharderwijk.nl |
:mace:dir:attribute-def:eduPersonEntitlement |
RFC-2141 URN
Multi-valued
to be determined per service (see Standardized values for eduPersonEntitlement) | |
urn:mace:dir:attribute-def:eduPersonPrincipalName |
UTF8 String
user@domain
piet.jønsen@example.edu not.a@vålîd.émail.addreß |
urn:mace:dir:attribute-def:isMemberOf |
RFC-2141 URN
Multi-valued
urn:collab:org:surf.nl urn:collab:org:clarin.org | |
urn:mace:dir:attribute-def:uid |
0. |
9. |
2342. |
19200300. |
100.1 |
. |
1 |
UTF8 String
(max 256 chars)
s9603145 flåp@example.edu | |
urn:mace:dir:attribute-def:preferredLanguage |
nl nl, en-gb;q=0.8, en;q=0.7 |
Note that not all identity providers might make all attributes available.
Detailed attribute descriptions
ID
See above.
Surname
ORCID |
urn
urn:oid |
Multiplicity
single-valued
Description
The surname of a person (including any words such as "van", "de", "von" etc.) used for personalisation; this can be a combination of existing attributes.
Notes
Given name
urn:mace | |
urn:oid | |
Multiplicity | single-valued |
Description | Given name / "name known by"; combinations of title, initials, and "name known by" are possible. |
Notes |
|
Common name
:1.3.6.1.4.1.5923.1.1.1.16 | http://orcid.org/0000-0002-1825-0097 | |
ECK ID | urn:mace:surf.nl:attribute-def:eckid | https://ketenid.nl/spv1/eacf3765ad342...cf3a11fe9cab2365f95da3e9965501f7c98e (Attribute made shorter for readability) |
SURF CRM ID | urn:mace:surf.nl:attribute-def:surf-crm-id | ad93daef-0911-e511-80d0-005056956c1a |
MS AuthnMethodsReferences | http://schemas.microsoft.com/claims/authnmethodsreferences | urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport http://schemas.microsoft.com/claims/multipleauthn |
Note that not all identity providers might make all attributes available.
(1) eduPerson Object Class Specification (201602): https://wiki.refeds.org/pages/viewpage.action?pageId=44957738
Info | ||
---|---|---|
| ||
SURFconext considers the attributes nlEduPersonOrgUnit, nlEduPersonStudyBranch and nlStudielinkNummer deprecated. When you register a new SP at SURFconext, these attributes will not be allowed for use with SURFconext. Existing IdP's and SP can use these attributes until further notice. |
Detailed attribute descriptions
Anchor | ||||
---|---|---|---|---|
|
See User identifiers.
Anchor | ||||
---|---|---|---|---|
|
urn |
:mace | urn:mace:dir:attribute-def: |
sn | |
urn:oid | urn:oid:2.5.4. |
4 |
Multiplicity |
single-valued |
Description
Full name.
Notes
For example, a typical name of a person in an English-speaking country comprises a personal title (e.g. Mr., Ms., Rd, Professor, Sir, Lord), a first name, middle name(s), last name, generation qualifier (if any, e.g. Jr.) and decorations and awards (if any, e.g. CBE).
...
Data type | UTF8 string (unbounded) |
Description | The surname of a person (including any words such as “van”, “de”, “von” etc.) used for Personalization; this can be a combination of existing attributes. |
Examples | Vermeegen 孝慈 |
Notes |
Anchor | ||||
---|---|---|---|---|
|
urn:mace | urn:mace:dir:attribute-def: |
givenName | |
urn:oid | urn:oid: |
2. |
5. |
Multiplicity
single-valued
Description
Name as displayed in applications
Notes
Email address
4.42 | |
Multiplicity | single-valued |
Data type | UTF8 string (unbounded) |
Description | Given name, also known as a first name, forename or Christian name / “name known by”; combinations of title, initials, and “name known by” are possible. |
Examples | Jan Klaassen |
Notes |
Anchor | ||||
---|---|---|---|---|
|
urn:mace | urn:mace: |
urn:mace
dir:attribute-def: |
cn | |
urn:oid | urn:oid: |
2. |
5. |
4.3 | |
Multiplicity | multi-valued |
Data type | UTF8 string |
Description
e-mail address; syntax in accordance with RFC 5322
Notes
- Multiple email addresses are allowed
- An email address is not necessarily the email address of this person at the institution.
- Do not use this attribute to uniquely identify a user. Use the NameId instead.
- A user's email address may change over time, or an IdP may allow a user to change this value themselves. This makes that attribute unsuitable for authentication and authorization purposes.
uid
(unbounded) | |
Description | Full name. |
Examples | Prof.dr. Mërgim Lukáš Vermeegen 加来 千代, PhD. |
Notes | For example, a typical name of a person in an English-speaking country comprises a personal title (e.g. Mr., Ms., Rd, Professor, Sir, Lord), a first name, middle name(s), last name, generation qualifier (if any, e.g. Jr.) and decorations and awards (if any, e.g. CBE). |
Anchor | ||||
---|---|---|---|---|
|
urn:mace | urn:mace:dir:attribute-def: |
displayName | |
urn:oid | urn:oid: |
2. |
16. |
840.1. |
113730. |
3.1. |
241 | |
Multiplicity | single-valued |
Data type | UTF8 string (unbounded) |
Description |
Name as displayed in applications | |
Examples | Prof.dr. Mërgim Lukáš Vermeegen 加来 千代, PhD. |
Notes |
- Ideally the uid is not only a login name/code but also an identifier that is guaranteed as being unique within the institution over the course of time. At the moment, there is no such guarantee.
- Use the NameId for unique identifiers in SURFconext rather than uid.
- Use the eduPersonPrincipalName attribute if a human-readable unique identifier is required
- A uid may contain any unicode character. E.g., "
org:surfnet.nl:joe von stühl
" is a valid uid. - SURFconext translates @-characters in the uid to underscores. Yes, this means that uids are not guaranteed to be unique.
...
|
Anchor | ||||
---|---|---|---|---|
urn:mace | urn:mace: |
dir:attribute-def: |
urn:oid | urn:oid: |
0. |
9. |
2342. |
19200300. |
100.1. |
3 |
Multiplicity |
multi-valued | |
Data type | RFC-5322 address (max 256 chars) |
Description |
e-mail address; syntax in accordance with RFC |
5322 |
Notes
Organization type
urn:mace | |
urn:oid | |
Multiplicity | single-value |
Description | designation of the type of organisationhttp://www.terena.org/registry/terena.org/schac/homeOrganizationType |
Notes |
|
Examples | m.l.vermeegen@university.example.org "very.unusual.@.unusual.com"@example.com mlv@[IPv6:2001:db8::1234:4321]; the |
Notes |
|
Anchor | ||||
---|---|---|---|---|
|
urn:mace | urn:mace:dir:attribute-def:uid |
urn:oid | urn:oid:0.9.2342.19200300.100.1.1 |
Multiplicity | single-valued (multi-valued in the specification, but within SURFconext only 1 value is allowed) |
Data type | UTF8 String (max 256 chars); use of spaces and @ -characters is discouraged. |
Description | The unique code for a person that is used as the login name within the institution. |
Examples | s9603145 |
Notes |
|
Anchor | ||||
---|---|---|---|---|
|
urn:mace | urn:mace:terena.org:attribute-def:schacHomeOrganization |
urn:oid | urn:oid:1.3.6.1.4.1.25178.1.2.9 |
Multiplicity | single-valued |
Data type | RFC-1035 domain string. The domain MUST be a secondary-level domain that is under control by the institution. Preferably, the institution's main domain name should be used. |
Description | The user's organization using the organization's domain name; syntax in accordance with RFC 1035. |
Examples | uniharderwijk.nl |
Notes |
|
Anchor | ||||
---|---|---|---|---|
|
urn:mace | urn:mace:terena.org:attribute-def:schacHomeOrganizationType |
urn:oid | urn:oid:1.3.6.1.4.1.25178.1.2.10 |
Multiplicity | single-value |
Data type | RFC-2141 URN (see Schac standard) |
Description | designation of the type of organization as defined on http://www.terena.org/registry/terena.org/schac/homeOrganizationType |
Examples | urn:mace:terena.org:schac:homeOrganizationType:int:university urn:mace:terena.org:schac:homeOrganizationType:es:opi |
Notes |
|
Anchor | ||||
---|---|---|---|---|
|
urn:mace | urn:schac:attribute-def:schacPersonalUniqueCode |
urn:oid | urn:oid:1.3.6.1.4.1.25178.1.2.14 |
Multiplicity | multi-value |
Data type | RFC-2141 URN (see SURFnet registry) |
Description | The user's student, employee, and/or member id as used in the university's internal systems |
Examples | urn:schac:personalUniqueCode:nl:local:example.edu:employeeid:x12-3456 urn:schac:personalUniqueCode:nl:local:example.nl:studentid:s1234567 |
Notes |
|
Anchor | ||||
---|---|---|---|---|
|
urn:mace | urn:mace:dir:attribute-def:eduPersonAffiliation |
urn:oid | urn:oid:1.3.6.1.4.1.5923.1.1.1.1 |
Multiplicity | multi-valued |
Data type | UTF8 String (only the values enumerated below are allowed) |
Description | Indicates the relationship between the user and his home organization (institution). The following values are permitted within SURFconext:
Use the above mentioned definitions to determine which affiliation a user gets. If the definitions are not sufficient, please use common sense. |
Examples | see above |
Notes |
|
Anchor | ||||
---|---|---|---|---|
|
urn:mace | urn:mace:dir:attribute-def:eduPersonScopedAffiliation |
urn:oid | urn:oid:1.3.6.1.4.1.1466.115.121.1.15 |
Multiplicity | multi-valued |
Data type | UTF8 String of the form affiliation@domain (see below) |
Description | Indicates the relationship between the user and the domain of his home organization. The affiliation part must be one of the allowed values of the eduPersonAffiliation attribute (see definition right above). The value is the role of the user and the domain name of the organisation. eduPersonScopedAffiliation can hence be defined as: <eduPersonAffiliation> "@" <schacHomeOrganization>. Just like eduPersonScopedAffiliation, this is a multi valued attribute. The domain part must be the schacHomeOrganization of the user (or a subdomain thereof). |
Examples | student@uniharderwijk.nl faculty@uniharderwijk.nl |
Notes |
|
Anchor | ||||
---|---|---|---|---|
|
urn:mace | urn:mace:dir:attribute-def:eduPersonEntitlement |
urn:oid | urn:oid:1.3.6.1.4.1.5923.1.1.1.7 |
Multiplicity | multi-value |
Data type | RFC-2141 URN |
Description | entitlement; custom URI (URL or URN) that indicates an entitlement to something. |
Examples |
|
Notes |
|
Anchor | ||||
---|---|---|---|---|
|
urn:mace | urn:mace:dir:attribute-def:eduPersonPrincipalName |
urn:oid | urn:oid:1.3.6.1.4.1.5923.1.1.1.6 |
Multiplicity | single-valued |
Data type | UTF8 String of the form user@scope |
Description | Unique identifier for a user. |
Examples | piet.jønsen@example.e not.a@vålîd.émail.addreß |
Notes |
|
Anchor | ||||
---|---|---|---|---|
|
urn:mace | urn:mace:dir:attribute-def:isMemberOf |
urn:oid | urn:oid:1.3.6.1.4.1.5923.1.5.1.1 |
Multiplicity | multi-valued |
Data type | RFC-2141 URN |
Description | Lists the collaborative organizations the user is a member of. |
Examples | urn:collab:org:surf.nl |
Notes |
|
Anchor | ||||
---|---|---|---|---|
|
urn:mace | urn:mace:dir:attribute-def:preferredLanguage |
urn:oid | urn:oid:2.16.840.1.113730.3.1.39 |
Multiplicity | single-valued |
Data type | RFC2798 BCP47 |
Description | a two-letter abbreviation for the preferred language according to the ISO 639 language abbreviation code table; no subcodes. |
Examples | nl |
Notes | Used to indicate an individual's preferred written or spoken language. This is useful for international correspondence or human-computer interaction. Values for this attribute type MUST conform to the definition of the Accept-Language header field defined in RFC 2068 with the exception that the value " |
Anchor | ||||
---|---|---|---|---|
|
urn:mace | urn:mace:dir:attribute-def:eduPersonTargetedID |
urn:oid | urn:oid:1.3.6.1.4.1.5923.1.1.1.10 |
Multiplicity | single-valued |
Data type | UTF8 string (unbounded) |
Description | The attribute eduPersonTargetedID is a copy of the persistent Subject -> NameID, which is generated by SURFconext itself. When an Identity Provider provides the eduPersonTargetedID itself, it is always overwritten by SURFconext. |
Examples | bd09168cf0c2e675b2def0ade6f50b7d4bb4aae |
Notes | This attribute is created because the Subject -> NameID itself is not part of the SAML v2.0 response and therefore only is available for an application if the local SAML implementation explicitly supports this. Within SURFconext the Subject -> NameID is explicitly copied into the |
Anchor | ||||
---|---|---|---|---|
|
urn:mace | urn:mace:dir:attribute-def:eduPersonOrcid |
urn:oid | urn:oid:1.3.6.1.4.1.5923.1.1.1.16 |
Multiplicity | multi-valued (see remark below) |
Data type | URL, registered with ORCID.org |
Description | The ORCID is a persistent digital identifier that distinguishes the account holder from every other researcher. Through integration in research workflows such as manuscript and grant submission, the ORCID identifier supports automated linkages between the account holder and his/her professional activities ensuring that the account holder's work is recognized. Values MUST be valid ORCID identifiers in the ORCID preferred URL representation, i.e. http://orcid.org/0000-0002-1825-0097 |
Examples | |
Notes | Although the attribute is in theory multi-valued, in practice it probably makes sense that it has no more than one value. |
Anchor | ||||
---|---|---|---|---|
|
...
urn:mace | urn:mace: |
surf.nl:attribute-def: |
eckid |
urn:oid |
Multiplicity
multi-valued
Description
Indicates the relationship between the user and his home organisation. The following values are permitted:
student
— studentemployee
— all employeesstaff
— academic staff
Notes
Identity providers might internally use additional values for the affilication attribute, such as alum
or affiliate
. Per SURFconext policy, such users are not allowed access to SURFconext.
Entitlements
urn:mace | |
urn:oid | |
Multiplicity | multi-value |
Description | entitlement; custom URI (URL or URN) that indicates an entitlement to something. |
Notes |
|
- | |
Multiplicity | single-valued |
Data type | URL as specified by Edu-K, all-lowercase |
Description | Educatieve Content Keten Identifier (ECK ID) is a pseudonymous identifier for access to content for primary, secondary and vocational education. |
Examples |
|
Notes | This attribute may only be used for “the access to and use of digital learning resources or the digital administration of tests and exams”. For more information see https://www.eck-id.nl (Dutch). Also, if you query this claim information from an external data stores, such as an Enterprise Active Directory, Lightweight Directory Access Protocol (LDAP) directories or a Microsoft SQL Server, you can also define custom attribute stores to query the ECK ID claim from external data stores. Read this Microsoft blog to get to know more. |
Anchor | ||||
---|---|---|---|---|
|
...
urn:mace | urn:mace: |
surf.nl:attribute-def: |
surf-crm-id | |
urn:oid | urn:oid:1.3.6.1.4.1.1076. |
20. |
100. |
10. |
50. |
2 | |
Multiplicity | single-valued |
Description
Unique identifier for a user.
Notes
- Although this value resembles an email address, it MUST NOT be used as an email address. In many cases mail cannot be delivered to this "address".
- Even though this value uniquely identifies a user, it is not guaranteed that it is persistent over sessions (even though it usually is).
- Do not use this to uniquely identify users. Use the NameId instead.
isMemberOf
urn:mace | |
urn:oid | |
Multiplicity | multi-valued |
Description | Lists the collaborative organisations the user is a member of. |
Notes |
|
Preferred Language
urn:mace | |
urn:oid | |
Multiplicity | single-valued |
Description | a two-letter abbreviation for the preferred language according to the ISO 639 language abbreviation code table; no subcodes. |
Notes | Used to indicate an individual's preferred written or spoken language. This is useful for international correspondence or human-computer interaction. Values for this attribute type MUST conform to the definition of the Accept-Language header field defined in RFC 2068 with one exception: ?the value " |
Data type | Microsoft GUID |
Description | GUID of the organization to which the IdP belongs, as used in the SURF CRM. |
Examples | ad93daef-0911-e511-80d0-005056956c1a |
Notes | SURF specific and only to be used by SURF SPs that have to interface with the SURF CRM. Only to be used after consultation with SURFnet. |
Anchor | ||||
---|---|---|---|---|
|
Name | http://schemas.microsoft.com/claims/authnmethodsreferences |
Multiplicity | multi-valued |
Data type | URI |
Description | The AuthnContext-referenties involved in authenticating the current user on their home IdP. |
Examples |
|
Opmerkingen |
|
...