Linking Issues with ebrary
I'd like to thank Chip Stewart (CCNY) , Songqian Lu (NYCCT), and Kenneth Rosenberg (QC) for bringing a couple of problems with linking to ebrary to my attention. The two issues were
1) After connecting to an ebrary book through the (proxied) catalog, the ebrary account login function did not work properly, and
2) Outgoing links to ebrary from an SFX menu produced EZproxy error messages.
The underlying issue is that ebrary, when used with its SSO mechanism, should *not* be proxied anywhere. The reason for that is that the control over the authentication process is handled entirely by ebrary (not by the proxy server). For those of you who administer EZproxy configuration, this is described in the following places:
- EZproxy: ebrary database setup:
http://www.oclc.org/support/documentation/ezproxy/db/ebrary.htm
- ebrary EZProxy Single Sign On (SSO):
http://site.ebrary.com/lib/support/docDetail.action?docID=80019166
So in your proxy configuration file, you should only have the following 2 lines:
Option ebraryUnencodedTokens
ebrarySite [your channelname]
(Note: there is no H(ost) or D(omain) statement)
In addition, I had to make sure that the ebrary target in SFX is *not* proxied, so outbound ebrary URLs never have a proxy prefix. This has been put in place for the locations whose EZproxy server is managed by OLS.
I'd appreciate if the members of the SFX Committee could briefly test access to ebrary in a variety of settings (through the catalog, off-campus, through SFX) just to make sure things are working now. If you encounter problems, please report them by openeing a work order with the help desk.
- roland.samieske's blog
- Login or register to post comments
