KNF:Attributen overzicht voor Service Providers/en: verschil tussen versies
|Regel 76:||Regel 76:|
[[Categorie:Entree Federatie Service Provider]]
Versie van 16 aug 2018 15:42
To authenticate and subsequently authorize a user the Entree Federation uses attributes. These attributes contain information (for example a firstname) about the user who wants access to a connected Service Provider.
There are two types of attributes used within the context of Entree Federation:
- Standard attributes
- Additional attributes
For most Service Providers the set with standard attributes will suffice to authenticate and authorize users. However there are situations in which a Service Provider requires more information about a user. In this case one or more additional attributes can be used.
In this table you can find the attributes that a Service Provider will always receive from Entree Federation.
|uid||Unique ID for the user. This is a encrypted version of the username and employeeNumber, followed by the realm||hash@realm||qj7cks8qdz9ph54@petteflat|
|givenName 1||First name||string||Piet|
|eduPersonAffiliation||Role||student, employee, staff or affiliate||student|
|nlEduPersonHomeOrganizationId||BRIN code of the institution||4 or 6 characters||11ZZ03|
|nlEduPersonHomeOrganization||Name of the institution||string||Petteflat College|
1 Attention: During the implementation of the coupling the Service Provider can choose to receive either the first name or the surname. If the Service Provider prefers to receive both names the school has to sign an Attribute Release Policy form.
The Service Provider will only receive these attributes when the school has given explicit permission by signing an Attribute Release Policy form.
|nlEduPersonRealId 1||Unencrypted version of the uid||[userId]@[realm]||pietjepukkelen@petteflatcollege|
|givenName 2||First name||string||Pietje|
|homePostalAddress||Address||Maximum of 6 lines each containing a maximum of 30 characters||Petteflat 121e |
|nlEduPersonBirthDate||Date of birth||yyyymmdd||19801231|
|nlEduPersonProfile||Name of study preceded by CREBO<space>.
Optionally BOL_ or BBL_ can be added at the beginning
|nlEduPersonDepartment||Department or sector||string||Techniek|
|nlEduPersonUnit||Primary class or group. Unique within the school administration or domain||string||H2A|
|ou||Class or group||string||H2A|
If a school has multiple administrations the administrationnumber can be added after the @ as in the example
In accordance with annex I and II, corresponding to Article 1 of the Regulation of the Minister of OCW containing the determination of the elementcode table and studycode table for secondary and adult education: nr. DUO/OND-2013/15135 M.
In accordance with annex I and II, corresponding to Article 1 of the Regulation of the Minister of OCW containing the determination of the elementcode table and studycode table for secondary and adult education:: nr. DUO/OND-2013/15135 M.
1 Attention: The encrypted version of this attribute will always be passed on to Service Providers. To pass on the unencrypted version the school has to sign an Attribute Release Policy.
2 Attention: During the implementation of the coupling the Service Provider can choose to receive either the first name or the surname. If the Service Provider prefers to receive both names the school has to sign an Attribute Release Policy form.
Attribute release policy
A school can give permission to pass on certain additional attributes to a specific Service Provider by signing an Attribute Release Policy. An overview of Attribute Release Policies can be found at the Kennisnet support pages.