Uberflip Deprecating TLS 1.0 as of June 1, 2017

What is TLS?

TLS, otherwise known as "Transport Layer Security" is a protocol that provides privacy and data integrity between two communicating applications.

TLS is the most widely deployed security used today, and is intended for web browsers and other applications that require data to be securely exchanged over a network.

The main function of TLS is to ensure that a connection to a remote endpoint is the intended endpoint through encryption and endpoint identity verification. The versions of TLS, to date are TLS 1.0, 1.1 and 1.

What's Changing?

On June 1, 2017, Uberflip will be disabling the TLS 1.0 encryption protocol across all Uberflip services, and only supporting TLS 1.1 and TLS 1.2. Uberflip has already enabled TLS 1.1 and TLS 1.2.

TLS ensures that a connection to a remote endpoint is to the intended destination through encryption and endpoint identity verification. Uberflip web and API connections use TLS as a key component of their security.

After Uberflip disables TLS 1.0, any secure connections to your Uberflip account will need to use the TLS 1.1 or TLS 1.2 encryption protocol. This change will impact secure access to Uberflip services, including

This change will not impact access to Uberflip-hosted non-secure flipbooks and hubs (“non-SSL” flipbooks and hubs).

Why the Change?

TLS 1.0 has several limitations and vulnerabilities that have been addressed in TLS 1.1 and TLS 1.2. Industry best practice is to disable TLS 1.0 and only support TLS 1.1 and TLS 1.2 on secure websites, web applications, and APIs.

When is the Change Happening?

June 1, 2017 for all Uberflip services.

What do I need to do to be prepared for this change?

Web browsers

You, your organization’s users, and visitors to your secure flipbooks and hubs (“SSL-enabled” flipbooks and hubs) will experience issues accessing Uberflip using web browsers which do not support TLS 1.1 or TLS 1.2, or which have been configured to disable these protocols.

The following tables summarize most major web browser versions’ compatibility with TLS 1.1 and TLS 1.2. You are encouraged to confirm your browser’s compatibility with its documentation and test compatibility with TLS 1.1 or TLS 1.2 before TLS 1.0 is deprecated.

Google Chrome

Chrome 38 & Newer: Compatible by default

Chrome 22-37: Compatible on certain operating system versions by default

If you can view the test page without errors, your web browser will not be affected by this change. Otherwise, you will need to upgrade or reconfigure your web browser in order to continue accessing Uberflip when this change is made.

API Consumers

Integrations, connectors, and other “apps” will experience issues consuming Uberflip APIs using languages, frameworks, or client libraries which do not support TLS 1.1 or TLS 1.2, or which have been configured to disable these protocols.

The following tables summarize most major platforms’ compatibility with TLS 1.1 and TLS 1.2. You are encouraged to confirm your platform’s compatibility with its documentation and test compatibility with TLS 1.1 or TLS 1.2 before TLS 1.0 is deprecated.