Re: [IUG] EZproxy and Patron API

[Heather Tucker <Heather dot Tucker at mhcc dot edu>]

I just wanted to thank everyone who chimed in on this issue.  In the end everyone was correct: ArtSTOR does work with WAM.  Our problem ended up being that ArtSTOR had one of our IP ranges wrong on their end.  Cue forehead smack.

Our eBrary issue seems to be a problem with the "bookshelf" function, which uses https and triggers a domain mismatch message, as discussed here:  http://innovativeusers.org/list/archives/2007/msg05963.html  It's not the end of the world, but it confuses our students.

Seeing as EZproxy won't fix that either, we are considering installing a wildcard SSL certificate.  Has anyone successfully implemented a wildcard cert?
We've read that wildcard certs can cause problems in Firefox.  Should we just step away from the SSL certificate?  Any opinions or advice off-list would be appreciated.

Thanks,
Heather

Heather Tucker wrote:
> Hi all,
>
> We are interested in installing EZproxy for remote access to our databases.  We currently use the Innovative rewrite proxy which doesn't work with many of our resources, like eBrary and Artstor.  Computer Services on our campus uses Active Directory Application Mode for student information and we've been unable to get it to work with EZproxy.  Compounding this, CS doesn't regularly expunge old student records so this isn't the best option.
>
> We looked into using III to authenticate patron info, but this would
> seemingly require purchasing the Patron API.  Does anyone know of a
> workaround that is less cumbersome than what people came up with in
> 2001?  (Found here:
> http://www.innovativeusers.org/list/archives/2001/msg03568.html)
>
> Barring that, does anyone successfully use ADAM with EZproxy?
>
> Thanks in advance,
>
> Heather Tucker, MLIS
> Technical Services Coordinator
> Mt. Hood Community College
> 26000 SE Stark St.
> Gresham, Oregon 97036
> 503-491-7106
> heather dot tucker at mhcc dot edu<mailto:heather dot tucker at mhcc dot edu>



--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---