TLS 1.0 Deprecation starting on July 22, 2017

Starting on July 22, 2017, Inkling will require that all connections use Transport Layer Security (TLS) v1.1 or higher. This change is being made to ensure that we continue to meet the security requirements laid out in the SOC2 audit now that numerous vulnerabilities that have been announced with the TLS v1.0 protocol. After making this change, Inkling will be better in line with industry best practices around use of the TLS protocol.


We are providing advance notice to customers so that there is adequate time to ensure that TLS 1.0 clients are upgraded to their latest versions. We highly recommend that users upgrade to the latest versions of any major browsers or clients to stay up to date with security fixes. The following is a list of browser versions and clients that Inkling will support starting on July 22, 2017. Starting on this date, clients using the TLS 1.0 protocol will be unable to access Inkling. You can test for TLS 1.1 and 1.2 compatibility by using the following link in your web browser:




Android KitKat (4.4)

or higher


Chrome 38 or higher


Chrome 22 through 27

Compatible when using Windows XP SP3, Vista or newer; Mac OS X Snow Leopard (10.6) or newer; Android Gingerbread (2.3) or newer

Firefox 27 or higher


Firefox 23 through 26

Compatible after configuration change. Use about:config to change security.tls.version.max to 3

Internet Explorer 11

(Desktop and mobile)


Microsoft Edge


Safari 7 or higher

on OS X Mavericks (10.9) or higher


Mobile Safari 5 or higher

on iOS 5 or higher


Other clients (API clients)

Any other clients including those interacting with Inkling’s APIs will need to upgrade their HTTP and/or SSL libraries to support TLS 1.1 or later

Subversion (SVN) Clients

Not impacted by this change


Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk