...

JSTOR provides persistent URLs such that the same persistent URL that is used by other authentication means (eg. IP authentication) also can be used as the RESOURCE-LOCATION url when creating WAYFless URLs as described above.  For instance, http://www.jstor.org/stable/3912141^{Image Removed}, is a persistent link to The Science Newsletter.  This same url can be used directly to create a WAYFless URL: http://www.jstor.org/start-session?entityID=urn:mace:incommon:university.edu&target=http%3A%2F%2Fwww.jstor.org%2Fstable%2F3912141

The fact that the same URL can be used to create the WAYFless URL, this makes implementation via EZproxy very straightforward.  EZproxy provides a mechanism, called SPUEdit, for rewriting URLs and redirecting browsers to the new rewritten URL.  This SPUEdit functionality allows EZproxy to create a WAYFless URL from a persistent link.  In the case of JSTOR, an SPUEdit directive in EZproxy can be defined as follows:

SPUEdit @^https*://.\{}.jstor\.org.$@HTTP$@http://www.jstor.org/start-session?entityID=urn:mace:incommon:university.edu&target=$e0@irs^{Image Added}

The SPUEdit is

 a regular expression rule.  In this example, *\^https*://.\.jstor\.org.$*, is the URL pattern that is matched in the regular expression.  And *http://www.jstor.org/start-session?entityID=urn:mace:incommon:university.edu&target=$e0* is the URL that is created from the regular expression.  \[The $e0 in this example is the entire matched pattern encoded\]  When EZproxy processes a URL, for instance,

http://ezproxy.university.edu/login?url=http://www.jstor.org/stable/3912141^{Image Added}

the URL will match the SPUEdit pattern, and redirect the user's browser through a WAYFless URL:

http://www.jstor.org/start-session?entityID=urn:mace:incommon:university.edy&target=http%3A%2F%2Fwww.jstor.org%2Fstable%2F3912141^{Image Added}

Example 2:

HW Wilson Web provides persistent URLs.  However, the persisten URLs that are used to create WAYFless URLs for HW Wilson Web are not the same persistent URLs that are used by other authentication methods.  For instance, a persistent URL for Visual Arts:the state of the art is

http://vnweb.hwwilsonweb.com/hww/jumpstart.jhtml?recid=0bc05f7a67b1790e22c948a92294d51df84446d22ac499870f2fecb1b0400d7c102b0ca3d14413a7&fmt=C^{Image Added}.

A Shibboleth authenticated direct link to the same resource though is a different URL structure,

https://vnweb.hwwilsonweb.com/cgi-bin/shibenv.pl?recid=0bc05f7a67b1790e22c948a92294d51df84446d22ac499870f2fecb1b0400d7c102b0ca3d14413a7&fmt=C^{Image Added}.

Notice that the difference between the two URLs:

http://vnweb.hwwilsonweb.com/hww/jumpstart.jhtml^{Image Added} <=> https://vnweb.hwwilsonweb.com/cgi-bin/shibenv.pl^{Image Added}

It turns out that the jumpstart.jhtml pattern can be consistently replaced by the shibenv.pl pattern across the HW Wilson Web platform in order to create WAYFless URLs.  The process is slightly more complicated, but can be handled by a SPUEdit directive in EZproxy:SPUEdit @^https*://vnweb\.hwwilsonweb\.com/hww/jumpstart\.jhtml?(.*)$@https://shib.oit.duke.edu/shibboleth-idp/SSO?shire=https%3A%2F%2Fvnweb.hwwilsonweb.com%2FShibboleth.sso%2FSAML%2FPOST&providerId=https%3A%2F%2Fvnweb.hwwilsonweb.com%2Fshibboleth&target=https%3A%2F%2Fvnweb.hwwilsonweb.com%2Fcgi-bin%2Fshibenv.pl%3F$e1@^{Image Added}
irs

Libraries