Skip to main content
OCLC Support

TLS security enhancements

Important information related to OCLC’s TLS security enhancements.

What you need to know about OCLC’s TLS security enhancements

To continue providing best-in-class security and to align with evolving industry standards, OCLC discontinued support for Transport Layer Security (TLS) versions 1.0 and 1.1.  

OCLC® systems accessed through the internet use the TLS encryption protocol for data protection. Internet browsers used to access OCLC systems need to use TLS version 1.2 or higher. Current versions of most browsers such as Chrome, Internet Explorer, Edge, Firefox, and Safari already accept TLS 1.2 or higher. Therefore, most members are not impacted and can continue to access OCLC systems as they do today.

For additional questions, please contact OCLC Support in your region.

Why did OCLC make this change

OCLC made this change because TLS versions 1.0 and 1.1 are older encryption protocols that the industry and the Internet Engineering Task Force are actively moving away from. Major browser companies, including Apple, Google, Microsoft, and Mozilla have announced that they will no longer support TLS versions 1.0 and 1.1. 

Impact of change on your access to OCLC systems

Any member accessing an OCLC system from a browser using TLS 1.0 or 1.1 will need to upgrade to a modern browser that uses TLS 1.2 or higher.

OCLC products impacted by this change include:

  • EZproxy (stand-alone, versions 6.2.1 and earlier)
  • ILLiad
  • Tipasa
  • WorldCat Discovery
  • WorldShare Acquisitions
  • WorldShare Circulation
  • WorldShare Collection Manager
  • WorldShare Interlibrary Loan
  • WorldShare License Manager
  • WorldShare Record Manager
  • WorldShare Report Designer

 

You can learn more about upgrading your browser by using the links below, or you can contact the IT support team at your organization for help.

OCLC API Users

OCLC API users will need to confirm that their client application(s) supports TLS 1.2 or higher. Please consult with the owner of your client application(s) to confirm how this should be done, as systems vary widely. Below are some examples of how you can check for a success message using three common programming languages.

PHP/Curl

curl https://tls-test.worldcat.org/

Python

import urllib.request

result = urllib.request.urlopen('https://tls-test.worldcat.org/')

result.read()

Ruby

require 'net/http'

response = Net::HTTP.get ('tls-test.worldcat.org', '/index.html')

response.body

STunnel connection

If you have trouble accessing OCLC systems, contact your organization’s IT support for assistance with upgrading STunnel to use TLS 1.2 or higher.

 

 

  • Was this article helpful?