Shibboleth Attribute Release meta-Policy

WARNING: This page is retained as a historical record but is out-of-date and is not being maintained.

This was a working document belonging to the Computing Service's Shibboleth Development Project. This project is complete (Raven now supports Shibboleth) and this document only remains for historical and reference purposes. Be aware that it is not being maintained and may be misleading if read out of context.

This document [2007-07-09: currently a draft] sets out the policy observed by the managers of the University of Cambridge's institutional Shibboleth IdP 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 Shibboleth Attribute Release policy summary for details of the currently implemented attribute rules.

Policy

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 SP, users are made aware of the attributes that will 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 University institutional IdP provides attribute information only to SPs operated by members of the UK Access Management Federation for Education and Research or by members of the local University of Cambridge Federation. Membership of the latter is restricted to SPs operated by the University and its related institutions.

4) Values for eduPersonTargetedID (an identifier allocated at random and distinct for each combination of user and SP, e.g. MlWd0XIR7juZvwvarOVdYiUWPW0=@cam.ac.uk), and the literal value member@cam.ac.uk for eduPersonScopedAffiliation, are released to any SP authorised to use the IdP. According to UK Federation policy, this should be sufficient to enable access to the majority of resources.

5) Values for eduPersonPrincipalName (e.g. 407-901-877@cam.ac.uk) and other values of eduPersonScopedAffiliation (in particular student@cam.ac.uk and staff@cam.ac.uk), may be released to any SP authorised to use the IdP that can demonstrate a reasonable need.

6) Values for any other attributes (in particular edPersonEntitlement, a 'catch-all' container for values specified by particular service providers, for example cam#default0 used by EduServ Athens to grant general access through the Shibboleth to Athens gateway), may be released to any SP authorised to use the IdP that can demonstrate 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. Each SPs will only receive the particular attributes and values that it requires.

7) Other attributes from or derived from lookup, notably givenName (e.g. Fred), sn (e.g. Clark), cn (e.g. F.J. Clark), displayName (e.g. Fred Clark), ou (e.g. Department of Important Studies), instid (e.g. IS), mail (e.g. fjc55@cam.ac.uk) and groupID (e.g. 100123, 100987) may be released to SPs operating on servers that can already query lookup directly for the same information, but only subject to the user's choice of suppression in lookup.

8) Other than as mentioned above, attributes and attribute values are only disclosed where there is a demonstrable need and where there is adequate levels of protection for the data concerned. Release of such information is only permitted where there is no alternative - it is in general preferable for SPs to obtain information direct from the user than it is for the University to supply it. Each decision to allow or alter 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.

Schedual

Attribute and attribute value disclosure approved under section 8 above:

None