[Wactclc-alma] Prepare now for ProQuest's HTTPS platform cutover

Wed May 24 12:12:00 PDT 2017

We had had some EZproxy problems which we addressed (with a new SSL certificate) but also a slightly different problem affecting ProQuest. I created a SF ticket three months ago (2/24). I dropped the ball in the exchange because things got busy and no one was complaining. This may not be at all related, but perhaps is interesting, at least.  If not, sorry for taking up so much space in your inbox ☺

-Sally

[Case #00394896]

2/24:  Should the 'http' parts of the parser parameters for ProQuest be 'https' instead [url=http://gateway.proquest.com/openurl & clientid=$$CLIENTID & url2=http://search.proquest.com<http://search.proquest.com/>]?

We have a problem linking from Primo to ProQuest resources which is similar to problems we had been experiencing before (symptoms in various vendor interfaces included delay/time out, lost CSS, non-functioning drop-downs).

Our software developer manages our ezproxy instance so I don't know all there is to know about it. We had been having issues with several databases that turned out to be due to our site certificate. This was only discovered when I called OCLC - our programmer was lost in the darkness. We now have a new site cert, per the recommendation of OCLC, found within the below text (what they sent me). Our programmer's last response to me (when I reported that though most issues were resolved, we still had issues linking from primo to proquest) was: "Can you make Primo talk to proquest via https? That seems like a good way to fix it to me."

OCLC had written in their follow-up email: "We had a look at your proxied sites you were having formatting and access issues on when proxied, and we were able to confirm that forcing an HTTPS connection through the proxy to Films On Demand fixed the issues (accepting the bad certificate).

To fix this permanently for all users, you can simply apply an SSL certificate to EZproxy that is properly configured. This would be a wildcard certificate issued to *.hope.whatcom.edu<http://hope.whatcom.edu/> (not *.whatcom.edu<http://whatcom.edu/> for reasons that are made clear in the documentation linked below) and should have a Subject Alternate Name (SAN) for hope.whatcom.edu<http://hope.whatcom.edu/>.

http://www.oclc.org/support/services/ezproxy/documentation/cfg/ssl.en.html
https://www.oclc.org/support/services/ezproxy/documentation/cfg/ssl/certopts.en.html"

-=-=-
4/6: Hi Sal,

I have investigated this case and Data Services did not find an issue with the ProQuest profile. Also, when testing on our end there is not a difference if the beginning is http or https. The http should open the resource.

The issue might be with the EZProxy or with the resource linking in Alma. When I reviewed the ProQuest profile, it does not seem to be using a proxy that should not be the issue.

Can additional information be provided with examples that are not working as expected? It would be great to have screen captures so we can see the behavior on your environment.

Thank you,
Greg

-=-=-
5/22: I can't remember the particulars; I am not certain but I think this was only an issue from off-campus. It seems to work on campus, and I asked someone to try to link to ProQuest from off-campus and it worked. I can't swear there isn't some lingering potential for problems, but I will assume not.

However, regarding the http vs https issue ....I have received notices from ProQuest. Notice the word REQUIRE below.

Subject line: Prepare now for ProQuest's HTTPS platform cutover

June 30, 2017. That's the day ProQuest will require you to access our ProQuest platform via HTTPS, enabling an encrypted, more secure way to communicate between browsers and our services.
...
-=-=-
5/23: Sally, thank you for the update. The change by ProQuest to HTTPS will occur on that date. It would be a good idea to white list that address. Typically HTTPS don't have an many issues but it is save to be prepared.

Regarding the issues experienced off-campus, we would need examples to look into those. We can be limited to what we can offer if we cannot reproduce the issue.

Regards,
Greg

From: Wactclc-alma [mailto:wactclc-alma-bounces at lists.ctc.edu] On Behalf Of Yasuda, Naoko
Sent: Wednesday, May 24, 2017 9:10 AM
To: WACTCLC Primo discussions <wactclc-primo at lists.ctc.edu>; wactclc-alma at lists.ctc.edu
Subject: Re: [Wactclc-alma] Prepare now for ProQuest's HTTPS platform cutover

Hi Laura,

In Alma, because at Highline we are linking all the ProQuest databases to the Community Zone, I think parser parameters (linking syntax) need to be updated by Ex Libris in an Alma CKB update like in the case of Springer Link that I found in the Knowledge Center:

Springer Link is moving to HTTPS protocol
https://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/Springer_Link_is_moving_to_HTTPS_protocol

We have updated the EZproxy stanza and the links on our website from HTTP to HTTPS. I’m not sure if anything needs to be done in Primo.

Thank you for bringing this up. I’d also like to hear what everyone is doing to prepare for the transition not just for ProQuest but also for other resources.

Naoko Yasuda
Highline College Library

From: Wactclc-primo [mailto:wactclc-primo-bounces at lists.ctc.edu] On Behalf Of Staley, Laura
Sent: Tuesday, May 23, 2017 12:40 PM
To: wactclc-alma at lists.ctc.edu<mailto:wactclc-alma at lists.ctc.edu>; wactclc-primo at lists.ctc.edu<mailto:wactclc-primo at lists.ctc.edu>
Subject: [Wactclc-primo] FW: Prepare now for ProQuest's HTTPS platform cutover

Hi, All –

We may need to make some edits in both Alma and Primo because of this change.

If anyone has already done this, and compiled a list of where they made their edits, I’d love to see it.

Thank you,

Laura Staley / RTC Library

From: ProQuest [mailto:info at go.proquest.com]
Sent: Saturday, May 20, 2017 8:00 AM
To: Staley, Laura
Subject: Prepare now for ProQuest's HTTPS platform cutover

HTTPS is coming. Don't lose access to your ProQuest products

View in Browser<http://links.proquest.mkt5049.com/servlet/MailView?ms=NTQxMDAzMDYS1&r=MzU0Njc5OTg0NzQS1&j=MTE2MzE4MDIwOAS2&mt=1&rt=0>

[Ensure security and privacy at your library]<http://links.proquest.mkt5049.com/ctt?kn=9&ms=NTQxMDAzMDYS1&r=MzU0Njc5OTg0NzQS1&b=0&j=MTE2MzE4MDIwOAS2&mt=1&rt=0>

Getting HTTPS-ready is easy … and necessary.

June 30, 2017. That's the day ProQuest will require you to access our ProQuest platform via HTTPS, enabling an encrypted, more secure way to communicate between browsers and our services.

Is your library ready? Starting June 30, products based on the ProQuest platform will be accessible only through URLs and proxies that have been updated to HTTPS.

Why it matters. The ProQuest platform is the most-accessed of our platforms, and we don't want you to lose a moment of functionality. Throughout 2017 many other ProQuest products and services will be moving to HTTPS-only access as well.

What you can do today. You can set up your systems for HTTPS right now, well ahead of the June 30 cutover. Visit the Support Center<http://links.proquest.mkt5049.com/ctt?kn=13&ms=NTQxMDAzMDYS1&r=MzU0Njc5OTg0NzQS1&b=0&j=MTE2MzE4MDIwOAS2&mt=1&rt=0> for the ProQuest HTTPS timeline and a Library Checklist to configure proxies and URLs.

Visit Support Center<http://links.proquest.mkt5049.com/ctt?kn=3&ms=NTQxMDAzMDYS1&r=MzU0Njc5OTg0NzQS1&b=0&j=MTE2MzE4MDIwOAS2&mt=1&rt=0>

[Visit proquest.com]<http://links.proquest.mkt5049.com/ctt?kn=25&ms=NTQxMDAzMDYS1&r=MzU0Njc5OTg0NzQS1&b=0&j=MTE2MzE4MDIwOAS2&mt=1&rt=0>

789 East Eisenhower Parkway
Ann Arbor, MI 48108 USA

[Facebook]<http://links.proquest.mkt5049.com/ctt?kn=16&ms=NTQxMDAzMDYS1&r=MzU0Njc5OTg0NzQS1&b=0&j=MTE2MzE4MDIwOAS2&mt=1&rt=0>

[Twitter]<http://links.proquest.mkt5049.com/ctt?kn=5&ms=NTQxMDAzMDYS1&r=MzU0Njc5OTg0NzQS1&b=0&j=MTE2MzE4MDIwOAS2&mt=1&rt=0>

[LinkedIn]<http://links.proquest.mkt5049.com/ctt?kn=24&ms=NTQxMDAzMDYS1&r=MzU0Njc5OTg0NzQS1&b=0&j=MTE2MzE4MDIwOAS2&mt=1&rt=0>

[Pinterest]<http://links.proquest.mkt5049.com/ctt?kn=10&ms=NTQxMDAzMDYS1&r=MzU0Njc5OTg0NzQS1&b=0&j=MTE2MzE4MDIwOAS2&mt=1&rt=0>

[YouTube]<http://links.proquest.mkt5049.com/ctt?kn=23&ms=NTQxMDAzMDYS1&r=MzU0Njc5OTg0NzQS1&b=0&j=MTE2MzE4MDIwOAS2&mt=1&rt=0>

[Google+]<http://links.proquest.mkt5049.com/ctt?kn=14&ms=NTQxMDAzMDYS1&r=MzU0Njc5OTg0NzQS1&b=0&j=MTE2MzE4MDIwOAS2&mt=1&rt=0>

You are receiving this mailing based on your ProQuest subscription preferences.
Update your preferences.<http://links.proquest.mkt5049.com/ctt?kn=2&ms=NTQxMDAzMDYS1&r=MzU0Njc5OTg0NzQS1&b=0&j=MTE2MzE4MDIwOAS2&mt=1&rt=0>

No longer interested in ProQuest emails?
Unsubscribe<http://links.proquest.mkt5049.com/ctt?kn=15&ms=NTQxMDAzMDYS1&r=MzU0Njc5OTg0NzQS1&b=0&j=MTE2MzE4MDIwOAS2&mt=1&rt=0>.

We value your privacy. View our privacy policies<http://links.proquest.mkt5049.com/ctt?kn=4&ms=NTQxMDAzMDYS1&r=MzU0Njc5OTg0NzQS1&b=0&j=MTE2MzE4MDIwOAS2&mt=1&rt=0>.

Ensure that you receive email from ProQuest. View our white list instructions<http://links.proquest.mkt5049.com/ctt?kn=27&ms=NTQxMDAzMDYS1&r=MzU0Njc5OTg0NzQS1&b=0&j=MTE2MzE4MDIwOAS2&mt=1&rt=0>.

[http://links.proquest.mkt5049.com/open/log/54100306/MzU0Njc5OTg0NzQS1/0/MTE2MzE4MDIwOAS2/1/0]

------ **This message has been scanned by Symantec Messaging Gateway at RTC.**
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ctc.edu/pipermail/wactclc-alma_lists.ctc.edu/attachments/20170524/cd3eebfe/attachment-0002.html>