New service from SAGE Journals Online

Page last modified on 23 November 2022, at 04:27 PM (initially posted on 12 August 2008)

SAGE Journals Online is the award-winning delivery platform that allows users to search over 500 journals in business, humanities, social sciences, and science, technology and medicine, and their related backfiles to retrieve peer-reviewed articles crucial to their research.

SAGE PublicationsSAGE Journals OnlineeduPersonScopedAffiliation1Yes

This service uses the Atypon SP entityID

WAYFless URL: For SAGE Journals Online, the format is:

The idp parameter is the entityID within the federation of the institution's Identity Provider (IdP). The redirectUri parameter is optional, but by default should be %2F. Users would be redirected to the SAGE portal homepage after they've signed in, but administrators may use that parameter to have users directed to a particular journal, or page within a site. Both parameter values should be URL encoded.

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


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 "", often written as:

It is used for the basic authorisation decision: does 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 value 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.

Users of other IdP software should check their documentation.