PathCAL

Page last modified on 22 March 2013, at 12:21 PM (initially posted on 6 October 2009)

PathCAL is a set of web-based tutorials designed to help students understand the basic pathological principles of disease by exploiting techniques in learning psychology.

Delivered online via a specially developed platform, PathCAL is an invaluable resource for medical students.

PathCAL is produced and published by the College of Medicine and Veterinary Medicine at the University of Edinburgh.

Org.ServiceShib.AttributeNotesRequired
College of Medicine and Veterinary Medicine, University of EdinburghPathCAL2.2.1eduPersonScopedAffiliation1Yes

WAYFless URL:
https://www.pathcal.ac.uk/Shibboleth.sso/Login?&target=https%3A%2F%2Fwww.pathcal.ac.uk%2Fshibboleth%2Fdologin.asp&entityID=<entityID>

(where <entityID> is the entityID of your organisation's IdP)

Please note that WAYFless URLs cannot be guaranteed to remain unchanged over time.

This service is available for subscription to UK HE, FE & research councils through JISC Collections.

Note:

1. The only attribute that an identity provider must release for its users to be able to access many services that are licensed for use by everyone at a particular organisation is eduPersonScopedAffiliation. This is a scoped attribute, which might, for example, have the value "member" in scope "uni.ac.uk", often written as:

member@uni.ac.uk

It is used for the basic authorisation decision: does uni.ac.uk subscribe to the service in question? If so, the user is allowed access. The service provider will maintain its own list of which organisations (scopes) can access its service. For allowed organisations, the federation's Technical Recommendations for Participants indicate that, in HE/FE, users with scoped affiliation values from the set {member, student, staff, faculty, employee} are typically authorised to access content licensed on the basis of the JISC Model Licence, while {affiliate, alum} are not.

While a Shibboleth identity provider can generate eduPersonScopedAffiliation statically by setting the required scope in attribute-resolver.xml, this should only be done when it is known that all users are authorised. Otherwise, the value can be picked up from your LDAP / Active Directory as described on the IdP setup page.