How to test if an Identity Provider is supporting the eduGAIN Attribute Profile
- 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.
Recommended Attributes in eduGAIN
The eduGAIN Attribute Profile recommends that Identity Providers implement the following attributes for all users:
| Attribute | Description |
|---|---|
| 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. Example: jdoe@example.org |
| 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. Example: john.doe@example.org | |
| eduPersonAffiliation | See the Controlled Vocabolaries. Multi-valued. Example: student;member or staff;member |
| eduPersonScopedAffiliation | See the Controlled Vocabolaries. Multi-valued. Example: staff@example.org;member@example.org |
| schacHomeOrganization | Example: example.org |
| schacHomeOrganizationType | See the Controlled Vocabolaries. Example: urn:schac:homeOrganizationType:int:university 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.
Configure the Attribute Resolver of a Shibboleth IdP
How the attribute resolver can be configured to generate the above attributes without having to change or modify the user directory, is for example, described in this guide provided by SWITCH on section called "2. Configure Attribute Resolver". Probably, most values can be generated on existing values that are already in a typical user directory (e.g. displayName can be generated dynamically from an existing given name and surname).
Configure the Attribute Filter of a Shibboleth IdP
To release the recommended attributes to a particular Service Provider with a Shibboleth Identity Provider, edit the file "/opt/shibboleth-idp/conf/attribute-filter.xml". The add the following code before the "</AttributeFilterPolicyGroup>" tag and change the entityID (https://sp.example.org/shibboleth) to the entityID of an actual Service Provider:
<!-- Example SP -->
<AttributeFilterPolicy id="Example-SP">
<PolicyRequirementRule xsi:type="basic:AttributeRequesterString"
value="https://sp.example.org/shibboleth" />
<afp:AttributeRule attributeID="displayName"><afp:PermitValueRule xsi:type="basic:ANY"/></afp:AttributeRule>
<afp:AttributeRule attributeID="commonName"><afp:PermitValueRule xsi:type="basic:ANY"/></afp:AttributeRule>
<afp:AttributeRule attributeID="email"><afp:PermitValueRule xsi:type="basic:ANY"/></afp:AttributeRule>
<afp:AttributeRule attributeID="eduPersonPrincipalName"><afp:PermitValueRule xsi:type="basic:ANY"/></afp:AttributeRule>
<afp:AttributeRule attributeID="eduPersonAffiliation"><afp:PermitValueRule xsi:type="basic:ANY"/></afp:AttributeRule>
<afp:AttributeRule attributeID="eduPersonScopedAffiliation"><afp:PermitValueRule xsi:type="basic:ANY"/></afp:AttributeRule>
<afp:AttributeRule attributeID="schacHomeOrganization"><afp:PermitValueRule xsi:type="basic:ANY"/></afp:AttributeRule>
<afp:AttributeRule attributeID="schacHomeOrganizationType"><afp:PermitValueRule xsi:type="basic:ANY"/></afp:AttributeRule>
</AttributeFilterPolicy>