Registry of Resources [DRAFT]
This page is created to collect information about resources that we have contacted and are in various stages of Shibboleth-compliance. The intent is this registry is twofold: to provide a checklist for vendors for Shibboleth implementation, and to provide implementation details to universities who would like to integrate with Shibboleth-enabled resources.
This Registry and the criteria for resource compliance will be fleshed out by the Vendor Subgroup through its contact with the priority target resources. The current chart below is a draft of the compliance checklist.
Vendor |
Resource |
Status |
Shibboleth-enabled |
InCommon Member |
SessionInitiators |
Shibboleth Attributes |
Features |
Contact |
Documentation |
EZP example |
|---|---|---|---|---|---|---|---|---|---|---|
Elsevier |
ScienceDirect, Scopus |
In production |
Yes |
Yes |
Yes |
https://shib.some-institute.edu/idp? |
|
|
Accessing ScienceDirect: Initiating a Shibboleth Authentication Request from a library home page or other customer portal |
Johns Hopkins Example SPUEdit -IncludeIP @^https*://.*\.sciencedirect\.com/.*$@https://shibboleth.johnshopkins.edu/shibboleth-idp/SSO?target=$e0&shire=https%3A%2F%2Fsdauth.sciencedirect.com%2FSHIRE&providerId=https%3A%2F%2Fsdauth.sciencedirect.com%2F@irs |
JStor |
|
In production |
Yes |
Yes |
Yes |
http://www.jstor.org/start-session?entityID=provider-uri&target=target-url |
|
|
Johns Hopkins Example SPUEdit -IncludeIP @^http*://.*\.jstor\.org/.*$@HTTP://www.jstor.org/start-session?entityID=urn:mace:incommon:johnshopkins.edu&target=$e0@irs |
|
EbscoHost |
|
In Production |
Yes |
Yes |
Yes |
Format 1: 
|
|
|
|
Johns Hopkins Example
SPUEditVar idpId=http://shibboleth.ebscohost.com
SPUEdit -IncludeIP @^https*://.*\.ebscohost\.com/.*$@https://shibboleth.johnshopkins.edu/shibboleth-idp/SSO?target=https%3a%2f%2fshibboleth.ebscohost.com%2fShibAgent.aspx%3fshib_returl%3d$e0&shire=https%3a%2f%2fshibboleth.ebscohost.com%2fShibboleth.sso%2fSAML%2fPOST&providerId=${idpId}@irs
|
|
|
|
|
|
|
|
|
|
|
|
Column desriptions:
Vendor: vendor's name
Resource: the particular resource in question, since many vendors have multiple platforms
Status: vendor/resource's status of Shibboleth implementation. This may even be that the vendor does not intend to implement Shibboleth
Shibboleth-enabled: whether or not the resource is Shibboleth-enabled, also what version of Shibboleth service provider
InCommon Member: whether or not the vendor is an InCommon member
SessionInitiators: whether or not resource is implemented with SessionInitiators and can work with the ezproxy workflow to bypass WAYF
Shibboleth Attributes: if there is a standard set of attributes resource expects, it will be identified here
Features: a place to list features such as personalization features
Help: contact information and/or links to configuration information or how tos