If you’re looking for a COTS solution, take a look at http://www.edulib.com/products/muse-proxy/overview/.  This product is integrated with our federated search platform, and has worked quite well for us in that capacity.  It has several advantages over EZproxy, and can be rather affordable for licensing.

-- 
Andrew Anderson, Director of Development, Library and Information Resources Network, Inc.
http://www.lirn.net/ | http://www.twitter.com/LIRNnotes | http://www.facebook.com/LIRNnotes

On Jan 16, 2015, at 16:06, Brett Bonfield <[log in to unmask]> wrote:

> Thanks for these responses. First, an update on EZProxy. I got a quote from
> OCLC. As I suspected, we can't afford it.
> 
> I'd prefer not to require cardholders to come to the library to create an
> approved account, though it's an interesting option. I'll follow up with
> NYT to see if that's an option that's available to us.
> 
> Thanks, Louis, for the links to the earlier conversation. I guess my hope
> was, since we just need a relatively small subset of what EZProxy can do,
> we might be able to get away with a cheap or free, and simple to implement
> and maintain, way of solving this specific problem. It feels like all we
> need is
> 
> Input: Designated numerical range (e.g. 122222222222-182222222222)
> Output: Static IP
> 
> I know it's more complicated than that, but it *seems* so easy.
> 
> Thanks again,
> 
> Brett
> 
> 
> On Thu, Jan 15, 2015 at 5:48 PM, Cornel Darden Jr. <[log in to unmask]
>> wrote:
> 
>> Hello,
>> 
>> Squid-url if it hasn't been already suggested. It's open source.
>> 
>> Thanks,
>> 
>> Cornel Darden Jr.
>> MSLIS
>> Library Department Chair
>> South Suburban College
>> 7087052945
>> 
>> "Our Mission is to Serve our Students and the Community through lifelong
>> learning."
>> 
>> Sent from my iPhone
>> 
>>> On Jan 15, 2015, at 4:03 PM, Louis St-Amour <[log in to unmask]>
>> wrote:
>>> 
>>> Can’t speak to the NYT stuff, but as for DIY proxying (as an alternative
>> to EZproxy), a starting point might be:
>> [log in to unmask]" target="_blank">https:[log in to unmask]
>>> 
>>> Besides price, here are some of the reasons why you might want to:
>> [log in to unmask]" target="_blank">https:[log in to unmask]
>>> 
>>> Myself, as a dev, I’d want to investigate a solution based around
>> something caching and fast like Varnish, but there’s nothing pre-made out
>> there like EZproxy right now, so it’s what everybody uses.
>>> --
>>> Louis St-Amour
>>> Sent with Airmail
>>> 
>>> On January 15, 2015 at 4:39:39 PM, Brett Bonfield ([log in to unmask])
>> wrote:
>>> 
>>> We've noticed that people almost never read the New York Times in print
>>> here at the Collingswood (NJ) Public Library, an independent,
>>> single-branch, municipal public library serving 18,000 people. But we
>>> believe they'll be very interested in reading the NYT online.
>>> 
>>> Online access costs about the same for us as print. We get unlimited
>> onsite
>>> access based on IP authentication, which is great: we have static IPs
>>> associated with WiFi access, public workstations, and staff computers.
>>> 
>>> We also get 10-20 passes (based on price), good for unlimited offsite
>>> access, that expire every 24 hours. But for offsite access we need to
>>> provide IP authentication.
>>> 
>>> Typically, that means EZProxy. I'm pretty sure we can't fit EZProxy into
>>> our budget. But we need some way to make sure NYT knows that traffic to
>>> https://myaccount.nytimes.com/grouppass/access is coming from or through
>>> us. After we provide NYT with some form of IP authentication, our
>>> cardholders would then sign in with an email address and password and
>>> receive their 24-hour access.
>>> 
>>> All of our online access to other databases and services is through card
>>> numbers: we provide a range, and the service authenticates against that
>>> range, typically authorizing access via SIP as well. NYT isn't currently
>>> configured for that type of authentication.
>>> 
>>> We need to keep the solution inexpensive. Something like a $5/month
>> Droplet
>>> and simple to install and maintain open source software could work. Or an
>>> inexpensive hosted VPN that offers static IPs and can somehow be
>> configured
>>> to accept our card number range for authentication? Or...?
>>> 
>>> Thanks,
>>> 
>>> Brett
>>