[ List Archives Home ] [ Thread index for 2008 ] [ Date index for 2008 ] [ Author index for 2008 ]


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Gerry,

We have just implemented EZproxy and we're using the patron API to
authenticate against our patron database.  We have been very impressed.
Since EZproxy  is a URL re-writing proxy it's much simpler to have patrons
use rather than configuring their browser.  We are currently running the
Ezproxy beta that uses a single port for proxying and works behind
firewalls.  This has been very successful for us because as a medical
library we have a significant number of users trying to access resources
from behind hospital firewalls.  Also since you can configure everything by
site you can authenticate users and then redirect them back to your catalog
so that you can proxy journal resources without having to modify their URLs.

Let me know if you have any additional questions.

Tim Whisenant 
Systems Librarian 
University of Texas Health Science Center 
at San Antonio, Briscoe Library 
7703 Floyd Curl Dr. 
San Antonio, TX 78229 
ph:210-567-2400 fax:210-567-2490 
whisenant@xxxxxxxxxx 

-----Original Message-----
From: Gerry Clevenger [mailto:zzgclev@xxxxxxxxxx]
Sent: Friday, March 23, 2001 2:30 PM
To: innopac@xxxxxxxxxx
Subject: EZ Proxy


Are there any libraries using the EZ Proxy program?  Would you share
your experiences?  (We are using WAM)   I've bookmarked the Innovative
Proxy Server Knowledge Base website, but our Reference Task Force is
searching for a simpler solution for patrons. A member of our committee
had read something about this program and I was asked to query the
listserv.  Thanks!.

--
This message was distributed through the Innovative Users Group INNOPAC
list.
Private replies:  Gerry Clevenger <zzgclev@xxxxxxxxxx>
Public replies:   INNOPAC@xxxxxxxxxx
Archives:  http://innopacusers.org/list/archives/
--
This message was distributed through the Innovative Users Group INNOPAC list.
Private replies:  "Whisenant, Tim" <whisenant@xxxxxxxxxx>
Public replies:   INNOPAC@xxxxxxxxxx
Archives:  http://innopacusers.org/list/archives/