Quote:
Originally Posted by misc
First of all - jhowell - thank you *so* much for this completely life-changing plugin. It's incredible.
...
I'm out of ideas. Any suggestions?
|
I'm glad to hear that the plugin has been useful for you.
Setting it up to work with EBSCOhost can be difficult. Their authentication system is complex, with lots of possible variations. I wasn't able to test most of the possibilities with the few libraries I can access. It turns out that it doesn't properly handle the library you use.
Your library authenticates your credentials and then redirects your browser to EBSCOhost. You were correct in choosing
lib= as the authentication type to be used by the plugin.
FYI: The authtype of "ip,uid" embedded in the url is part of what your library passes to EBSCOhost and isn't directly relevant to configuring the plugin. ("ip" mean access is allowed for anyone connecting from a computer with an IP address registered as being located at the library. "uid" is the authentication type used otherwise.)
The comment you found on the web page, "user: s8333660.main.ehost", indicates that the customer id of your library is
s8333660, so that is what you should use as the library-id in the plugin configuration.
Looking at the log from the plugin, from the error message it appears that the login was actually successful, but the plugin did not recognize it properly. The plugin expects that it will be redirected to a host name ending in
ebscohost.com, but in your case the redirected host was
web.b.ebscohost.com.ezwx.ez.cwmars.org:58000.
I will update the plugin in the next few days to (hopefully) handle cases like this.
You may be able to work around the problem by signing in to EBSCOhost directly instead of through your library. To do this change the plugin configuration from
lib=... to
uid (just those three characters). It is not certain to work, but is worth a try.