1 260
szerkesztés
Módosítások
→eduPersonPrincipalName: disallow special chars
In a federation, information about the user is represented in SAML attributes transferred from the Identity Provider to the Service Provider. It is important for both parties to interpret the data in the same way.
Exact definitions of the attributes are maintained in the their defining schemas. Within this specification, we use the following schemas:
* ''person'', ''organizationalPerson'' (X.521)
* ''inetOrgPerson'' (RFC2798)
* ''eduPerson'' (http://middleware.internet2.edu/eduperson/, version 200806)* ''SCHAC'' (http://www.terena.org/activities/tf-emc2/schacreleases.html, version 1.4.1)
* ''niifPerson'', ''niifEduPerson'' ([[NIIFSchema]])
=== Persistent user identifiers ===
For some most services, it is necessary to store application-specific data, such as user edits for a wiki page. This data is stored in some a database , which is local to the SP, while the key between the user and the database entry is a the '''persistent user identifier'''.
Persistent identifiers can be:
* '''computed''': the identifier is generated run-time from one or more attributes of the user (usually by some cryptographic hashing algorithm).
* '''stored''': the identifier is stored in the user's digital identity at the IdP, thus it is persistent even when other user information is changed. Uniqueness of the identifier must be preserved.
* '''persistence''': IdPs must ensure that the identifier does not change during the life-cycle of the user at the institution.
* '''non-reassignable''': IdPs must ensure that an identifier of a user will not be reassigned to another user.
* '''opacity''': opaque identifiers are do not refer to any personal data
* '''targeted''': targeted identifiers are different for each SP, thus the SPs are unable to build common user profile without the cooperation of the IdP. Such identifiers are preferred from privacy reasons.
Persistent identifiers can be transferred in SAML attributes or in NameID of a SAML Assertion. Certain SP implementations (such as Shibboleth 2.x) can hide the details of the transfer, and can provide a persistent identifier in REMOTE_USER header.
=== List of attributes ===
In this specification, only mandatory and recommended attributes are specified. The [[HREFAttributeSpec|Hungarian version of the Attribute Specification]] contains descriptions of the optional attributes as well. If you have any questions regarding the optional attributes, please contact the Federation Operator.
==== eduPersonTargetedID ====
|implementation=mandatory
|syntax=Must be a SAML2 persistent NameID; the unique identifier part must not be no longer than 256 ASCII characters.
|example=
An IdP sends the attribute on the wire such as:
The application at the SP receives the attribute as the following:
https://idp.example.org/idp/shibboleth!https://sp.example.org/shibboleth!84e411ea-7daa-4a57-bbf6-b5cc52981b73
|assurer=institution
}}
eduPersonPrincipalName '''must not be reassigned'''
As some applications do not support special characters in identifiers, eduPersonPrincipalName MUST only contain the following characters: alpanumeric characters, dot ('.'), hyphen ('-') and underscore ('_').
|example=gipsz.jakab@example.org
|assurer=institution
}}
|description=Type of the Home Organisation
|semantics=
* '''university''': Higher Education institutions that are recognised by the Hungarian Ministry for Educationuniversities and colleges
* '''nren''': National research and educational network
* '''library''': Libraries
