Over four months ago we announced our commitment to securely connecting institutions and their users to ProQuest systems. The ProQuest platform, and many other ProQuest sites, have enabled HTTPS capability earlier this year, and other sites are still to come. This means that users’ private information and searches will stay as safe and secure as possible, no matter how and where they access ProQuest. All new ProQuest systems will run on HTTPS by default.

What’s changing?

We’re approaching the final phase when we’ll “sunset” our support of the legacy HTTP protocol and require connection to ProQuest systems with the more secure version, HTTPS.

As of July 10, 2017, the ProQuest platform will require the use of HTTPS for all search and document retrieval requests. Before then, libraries should make sure proxies and document links are adjusted. Since the ProQuest platform has the widest exposure of all of ProQuest's technologies, this change means we can help secure the largest bulk of your users’ search and document retrieval traffic as possible with one change. For other platforms we will sunset support of legacy HTTP connections later this year. For the full list of timing for the sunset of HTTP across all ProQuest products, review this support article, which will be regularly updated as dates are confirmed.

ProQuest URLs that use HTTP instead of HTTPS will still work through the transition. We will automatically redirect HTTP ProQuest URLs to their HTTPS versions.

What’s not changing?

The same ease of search, retrieval, saving and sharing will remain when using HTTPS rather than HTTP.

The “S” is for secure

HTTP (“hypertext transfer protocol”) dates back nearly 30 years, and in the recent past the use of HTTP is being actively transitioned to HTTPS (HTTP Secure) to enhance information security among Internet users.

Whether making a purchase on Amazon, doing online banking or using PayPal – or doing research via ProQuest resources – the use of HTTPS helps ensure an extra layer of security to protect things like user name and password and activity within the systems from being seen by unapproved eyes.

How you support internet privacy

As HTTPS is only effective when it is being used, librarians have a key role in making sure your systems and proxies are configured to use HTTPS full-time and bring the benefit of secure communications to patrons and users, all the time.

Resources to help …

Frequently Asked Questions

Question: Question: Why is ProQuest making this transition?

Answer: ProQuest is updating its services to better secure our products and our customers’ experience. Many sites are transitioning to HTTPS as it provides improved security overall.

Question: Why has the date changed from 30 June to 10 July?

Answer: The date was adjusted to ensure that this change was not affecting any customer institution’s month or fiscal-year end processes or the various national holidays that take place in early July.

Question: Can we update our ProQuest links to HTTPS before the July 10 transition?

Answer: Yes! We recommend changing the links as soon as possible to provide time to test the change. You will need to configure your proxy solutions for SSL/HTTPS before making the change. Please contact the proxy vendor support or consult their documentation for further instructions.

Question: The OCLC stanza does not appear to be updated for HTTPS. Will this be updated before the July 10 cutover?

Answer: Yes, we are working with OCLC to update the stanza on their website. For now, you’ll find the updated stanza on the ProQuest Support Center:

Question: How will HTTP URLs for ProQuest be handled after the transition?

Answer: ProQuest URLs that use HTTP instead of HTTPS will still work with the transition. We will automatically redirect HTTP ProQuest URLs to their HTTPS versions. To make these redirects work properly with your proxy solutions, make sure your proxy software is configured to work with SSL/HTTPS. See the OCLC website for instructions on doing this for EZproxy. For WAM proxy, contact Innovative Interfaces Support for assistance.

Question: How long will the redirect from HTTP to HTTPS be available?

Answer: We do not have any definitive timetable for the removing the redirect — so we ask that you update your links to HTTPS as soon as possible.

Question: What change must be made to our ProQuest URLs to account for the transition?

Answer: All you must do is change the HTTP:// in your URLs to HTTPS://. Additional configuration may be needed for your proxy solutions. Refer to the proxy vendor’s documentation or support teams for configuring these solutions for SSL/HTTPS.

Question: Some products are not listed in your announcement for HTTPS. Will these products be transitioned?

Answer: Depending on the product, they may be transitioned later as resources allow. Some products may be migrated to the ProQuest Academic platform at a later date, and some products may be discontinued. For details, contact ProQuest Technical Support.

Question: Does this transition impact Shibboleth/OpenAthens customers?

Answer: Our Shibboleth/OpenAthens authentication servers already support HTTPS and you can feel free to update your ProQuest URLs to the HTTPS versions now. There are no changes needed on your Shibboleth/OpenAthens servers as all changes will be handled on the server-side by ProQuest and the Federation from which you access ProQuest.

Question: Does this transition affect customers using Referring URL authentication?

Answer: Yes. Because of the way Referring URL information is passed, the website the ProQuest link is placed on (the referrer) must also be HTTPS. We recommend making sure that your library web pages support HTTPS before this transition happens or contact ProQuest Technical Support for alternative forms of authentication (Proxy Server, Barcode or Shibboleth/OpenAthens).

Question: Does this transition affect customers using Barcode Authentication?

Answer: Customers using Barcode Authentication should update their link to HTTPS, but in the meantime, the system will redirect them to the HTTPS version of the barcode authentication after the July 10 transition.