This document sets out the policy observed by the managers of the University of Cambridge's institutional Shibboleth Identity Provider (IdP), as provided by Raven, in respect of release of attribute information. Transfer of attribute information is central to the operation of Shibboleth, however attribute values may represent 'personal data' under the terms of the Data Protection Act 1998 and processing and release of such data must abide by the provisions of the act. This policy ensures that the University does so.
See the Shibboleth attribute release summary for details of the currently implemented attribute rules.
This version of the policy was approved at a meeting of the Computing Service Senior Management Team on 28th June 2011 (SMT paper 298).
1) All changes to this policy are approved by the Director of the University Computing Service or his deputy.
2) Users are told about the IdP, and the fact that it may disclose information about them, the first time they use it to access a resource and at least annually thereafter. They are required to positively confirm that they accept the terms and conditions under which the IdP operates before proceeding and a record is made of this acceptance. On first access to a particular Shibboleth Service Provider (SP), users are made aware of the attributes that may be disclosed to it, along with their current values, and asked to approve this disclosure; this will be repeated at least annually and any time the list of attributes being disclosed to this SP changes.
3) The Shibboleth protocol requires that the SP have a copy of the University's Shibboleth metadata. This is available via HTTPS at https://shib.raven.cam.ac.uk/shibboleth for ad hoc use by SPs outside our set of known access federations.
4) The University institutional IdP provides three attributes to any SP that requests them. These are:
4.1) eduPersonScopedAffiliation with appropriate values (e.g. email@example.com for members of the University, firstname.lastname@example.org for people entitled to access University Library-licenced electronic resources).
4.2) eduPersonTargetedID (an identifier allocated at random and distinct for each combination of user and SP, e.g. MlWd0XIR7juZvwvarOVdYiUWPW0email@example.com).
4.3) eduPersonPrincipalName with the value <crsid>@cam.ac.uk (e.g. firstname.lastname@example.org).
5) Values for any other attributes (in particular eduPersonEntitlement, a 'catch-all' container for values specified by particular SPs, for example urn:mace:oclc.org:100159623 on behalf of anyone entitled to access the general University Library electronic resource collection, as required by OCLC FirstSerach), are released where there is a reasonable need, providing the corresponding user's identity can not be derived from these attributes or other information likely to be available to the SP. Where appropriate, SPs will only receive the particular extra attributes and values that they require.
6) Other attributes from or derived from lookup, for example sn (e.g. Clark), displayName (e.g. Fred Clark), ou (e.g. Department of Important Studies), mail (e.g. email@example.com), University status (e.g. 'staff'), and groupID (e.g. 100123) may be released to SPs operated within the University, but only subject to the user's choice of suppression in lookup.
7) Other than as mentioned above, attributes and attribute values are only disclosed where there is a demonstrable need and where there are adequate levels of protection for the data concerned. Release of such information is only permitted where there is no alternative. Each decision to allow or alter such a particular disclosure is approved by the Director of the University Computing Service or his deputy before it is implemented and recorded in the schedule to this policy.
Attribute and attribute value disclosure approved under section 7 above: