- Which are the Recommended Attributes?
- Configure the Shibboleth IdP to release the Recommended Attributes to an example Service Provider.
- Test the release of the recommended attributes to the example Service Provider.
|eduPersonTargetedID/persistentID||Unique, persistent, opaque and targeted identifier of the user. |
(Serialized) Example: https://aai-logon.switch.ch/idp/shibboleth!https://filesender.funet.fi!yrVdvdAmohZY+cE6dcGvqu/Dubc=
|eduPersonPrincipalName||Unique, persistent identifier of the user. |
|displayName||Name and Surname of the user. |
Example: John Doe
|commonName||Name and Surname of the user. Could be multi-valued but it is recommended to have only one value.|
Example: Johne Doe
|User's personal eMail address.|
|eduPersonAffiliation||See the Controlled Vocabolaries. Multi-valued.|
Example: student;member or staff;member
|eduPersonScopedAffiliation||See the Controlled Vocabolaries. Multi-valued.|
|schacHomeOrganizationType||See the Controlled Vocabolaries. |
This attribute is unfortunately underspecified. Therefore, this attribute is of little use as of 2015.
How to configure the Recommended Attributes
The following paragraph describes how to support the recommended attributes listed above and how to create an attribute release rule to release the set of recommended attributes to a particular Service Provider. Please note that not all recommended attributes have to be release in general but only the ones that are required by the Service Provider.
Instead of manually configuring attribute release rules, you may also consider implementing the Data Protection Code of Conduct that (LINK NOT FOUND) that helps to automatically release attributes to a particular Service Provider that signed the Code of Conduct.
How to test the release of the recommended attributes to the Example Service Provider
The Shibboleth Identity Provider comes with a script called AACLI that allows to test the release of attributes:
If you have installed the Shibboleth IdP into its default path, you can execute the command