• BackLinks
• Search
• Print

Attributes

The core attributes used in the UK Federation are taken from the eduPerson specifications:

Both the old (200312) and new (200604) forms of eduPersonTargetedID are allowed within the federation and should be supported by service providers.

Attribute Sets

The attributes used within the federation have been categorised into Core Attributes, Subsidiary Attributes and Additional and Custom Attributes, as described in Attribute Sets.

A detailed discussion of attribute usage is given in Section 7 of Technical Recommendations for Participants but the core attributes are:

Attribute Usage

The table below shows the attributes recognised by a selection of services. This list is illustrative of attribute usage rather than comprehensive. It is intended to give new participants examples of how attributes are used in practice within the federation. It is not intended to list up-to-date attribute requirements for every service provider. (Identity providers should confirm the requirements directly with the service providers which their end users will access.)

Nevertheless, service providers can assist the community (and reduce their own support load) by asking the federation operator to list their attribute requirements here. To do so, email the federation helpdesk requesting an entry in this table and providing the following information:

• the name of the service;
• a brief description of the type of service offered, and who it is intended for;
• the URL of the log-in page for the service;
• the attributes used by the service;
• (where appropriate) the version number of the Shibboleth software used;
• any specific notes (such as whether additional attributes will give enhanced service).

(Entries in {...} brackets in the table below indicate that the information has not yet been provided.)

Of the attributes listed below, the only one that the default Shibboleth attribute release policy allows service providers to see is eduPersonScopedAffiliation. To release any others an identity provider needs to edit its arp.site.xml file (see Attribute Release, on the Attribute Usage Notes page).

Helpdesk | Privacy Policy | Website Info
© The JNT Association - JANET(UK), Lumen House, Library Avenue,
Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0SG
Tel: 01235 822200 Fax: 01235 822399