...
urn:mace | |
urn:oid | |
Multiplicity | single-valued |
Data type | UTF8 string (unbounded) |
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. |
Examples | Vermeegen 孝慈 |
Notes |
|
Given name
urn:mace | |
urn:oid | |
Multiplicity | single-valued |
Data type | UTF8 string (unbounded) |
Description | Given name / “name known by”; combinations of title, initials, and “name known by” are possible. |
Examples | Jan Klaassen |
Notes |
|
Common name
urn:mace | |||
urn:oid | |||
Multiplicity | multi-valued | ||
Data type | UTF8 string (unbounded) | ||
Description | Full name. | ||
Examples | Prof.dr. Mërgim Lukáš Vermeegen 加来 千代, PhD. | ||
Notes | For example, | 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). |
...
urn:mace | |
urn:oid | |
Multiplicity | single-valued |
Data type | UTF8 string (unbounded) |
Description | Name as displayed in applications |
Examples | Prof.dr. Mërgim Lukáš Vermeegen 加来 千代, PhD. |
Notes |
|
...
urn:mace | |
urn:oid | |
Multiplicity | multi-valued |
Data type | RFC-5322 address (max 256 chars) |
Description | e-mail address; syntax in accordance with RFC 5322accordance with RFC 5322 |
Examples | m.l.vermeegen@university.example.org "very.unusual.@.unusual.com"@example.com mlv@[IPv6:2001:db8::1234:4321] |
Notes |
|
...
urn:mace | |
urn:oid | |
Multiplicity | multi-valued |
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 flåp@example.edu |
Notes |
|
...
urn:mace | |
urn:oid | |
Multiplicity | single-valued |
Data type | |
Description | The user's organisation using the organisation’s domain name; syntax in accordance with RFC 1035. |
Examples | |
Notes |
|
...
urn:mace | |
urn:oid | |
Multiplicity | single-value |
Data type | |
Description | designation of the type of organisation as defined on http://www.terena.org/registry/terena.org/schac/homeOrganizationType |
Examples | |
Notes |
|
...
urn:schac:attribute-def:schacPersonalUniqueCode | |
Multiplicity | multi-value-value |
Data type | |
Description | The user's student, employee, and/or member id as used in the university's internal systems |
Examples | |
Notes |
|
...
urn:mace | |
urn:oid | |
Multiplicity | multi-valued |
Data type | |
Description | Indicates the relationship between the user and his home organisation. The following values are permitted:
|
Examples | |
Notes |
|
...
urn:mace | |
urn:oid | |
Multiplicity | multi-value |
Data type | |
Description | entitlement; custom URI (URL or URN) that indicates an entitlement to something. |
Examples | |
Notes |
|
...
urn:mace | |
urn:oid | |
Multiplicity | single-valued |
Data type | |
Description | Unique identifier for a user. |
Examples | |
Notes |
|
...
urn:mace | |
urn:oid | |
Multiplicity | multi-valued |
Data type | |
Description | Lists the collaborative organisations the user is a member of. |
Examples | |
Notes |
|
...
urn:mace | |
urn:oid | |
Multiplicity | single-valued |
Data type | |
Description | a two-letter abbreviation for the preferred language according to the ISO 639 language abbreviation code table; no subcodes. |
Examples | |
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 " |
...
Multiplicity | single-valued |
Data type | |
Description | The attribute eduPersonTargetedID is a copy of the Subject -> NameID which is generated by SURFconext itself. When an Identity Provider provides the eduPersonTargetedID itself, it is always overwritten by SURFconext. |
Examples | |
Notes | This attribute is created because the Subject -> NameID itself is not part of the SAML v2.0 response and therefore can not be used. Within SURFconext the Subject -> NameID is explicitly placed in the attribute eduPersonTargetedID, so that you can use it. |
...