[Wactclc-primo] EZProxy Update - version 7.1.1

[Guidry, Wade]

Thanks, Lily. Good info.

It does seem like surprising issues, since you upgraded from the most recent version.

The need to change http to https for the content URLs could have to do with a change in a default setting for one of the parameters. But I didn't see anything like that in the release notes.

The Kanopy issue sounds like a bug in the fresh version of EZProxy, unless some change in the Kanopy stanza is required, but nothing in the release notes about that either.

The release notes do say "This release is one of the biggest releases of EZproxy to date." They weren't kidding, I guess. Biggest also equals more chances to break.


Wade Guidry
Library Consortium Services Manager, WACTCLC
wadeg at bigbend.edu<mailto:wadeg at bigbend.edu>
(509) 760-4474
http://www.wactclc.org

From: Wactclc-primo <wactclc-primo-bounces at lists.ctc.edu> On Behalf Of Kun, Lily
Sent: Friday, February 26, 2021 1:21 PM
To: WACTCLC Primo discussions <wactclc-primo at lists.ctc.edu>
Subject: Re: [Wactclc-primo] EZProxy Update - version 7.1.1

CAUTION: Originated outside our network. Do not click links or open attachments unless you validate the sender.


My responses below...

Lily

From: Wactclc-primo <wactclc-primo-bounces at lists.ctc.edu<mailto:wactclc-primo-bounces at lists.ctc.edu>> On Behalf Of Guidry, Wade
Sent: Friday, February 26, 2021 12:54 PM
To: WACTCLC Primo discussions <wactclc-primo at lists.ctc.edu<mailto:wactclc-primo at lists.ctc.edu>>
Subject: Re: [Wactclc-primo] EZProxy Update - version 7.1.1

What version did you upgrade from? If it's an older version, a lot of stuff might have changed.
Lily: We usually keep it updated to the latest version. We're currently back to using version 7.0.16.

Some of the things that come to mind are proxy by port vs proxy by hostname (looks like you're already doing proxy by hostname, which is good).

Wildcard certificate for EZProxy is pretty much a requirement now. That might be part of the Kanopy issue (just a wild guess).
Lily: I think we already use wildcard certificate for EZProxy. Kanopy is working on the older version we've reverted back to, but not in 7.1.1. In the new version, Kanopy doesn't even resolve to the SPSCC login page-just gets an error message. OCLC Support was baffled when I demo'd it through WebEx for him. He also tried it on his end with the same results.

Interestingly, it looks like EZProxy now lets you fake a wildcard certificate<https://help.oclc.org/Library_Management/EZproxy/Configure_resources/Option_ForceWildcardCertificate>, if you don't have one. (since version 6)

The ForceHTTPSLogin config.txt setting might have an affect (it's now on by default).

When you say you changed the URLs on the library website, do you mean you added the 's' to the http:// for ezproxy, or for the reference to the database?
Lily: I added the "s" to the database URLs. I already changed to https for ezproxy a while back when many databases hadn't made the change, so that's why some of the databases haven't been updated with an "s". This change made all the other databases work except for Kanopy. Kanopy has always been a problem child of mine.

Looking at the release notes, I'm surprised at how much has changed in the past couple of years in EZProxy. They've really been doing a lot of development on it.


Wade Guidry
Library Consortium Services Manager, WACTCLC
wadeg at bigbend.edu<mailto:wadeg at bigbend.edu>
(509) 760-4474
http://www.wactclc.org

From: Wactclc-primo <wactclc-primo-bounces at lists.ctc.edu<mailto:wactclc-primo-bounces at lists.ctc.edu>> On Behalf Of Kun, Lily
Sent: Thursday, February 25, 2021 5:50 PM
To: WACTCLC Primo discussions <wactclc-primo at lists.ctc.edu<mailto:wactclc-primo at lists.ctc.edu>>
Subject: [Wactclc-primo] EZProxy Update - version 7.1.1

CAUTION: Originated outside our network. Do not click links or open attachments unless you validate the sender.


Hi Everyone,

Just thought I'd warn you about upgrading to the newest version of EZProxy. We upgraded to EZProxy 7.1.1 last week and it was a disaster. Many of our database links were not proxied and our users got an error message. I got lots of unhappy messages.

I fixed most of the database problems by updating the database URLs on the library website to https (don't know why this is an issue since most database sites just automatically switch you over to the https site...), but Kanopy refused to work at all, so we reverted back to the older EZProxy version. I have a ticket in with OCLC Support to look into the problem with Kanopy.

If you plan to upgrade to 7.1, then I recommend that you check all your database links immediately to make sure they all work. Hopefully, my experience was just a fluke and you'll have a smoother transition than I did.

Good luck!

Lily Kun
She/Her Pronouns
Systems and Electronic Resources Librarian
lkun at spscc.edu<mailto:lkun at spscc.edu> | 360-596-5436 | https://library.spscc.edu<https://library.spscc.edu/>

[cid:image001.jpg at 01D56E08.09265B00]<https://spscc.edu/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ctc.edu/pipermail/wactclc-primo_lists.ctc.edu/attachments/20210226/7409a4da/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 6993 bytes
Desc: image001.jpg
URL: <http://lists.ctc.edu/pipermail/wactclc-primo_lists.ctc.edu/attachments/20210226/7409a4da/attachment-0002.jpg>