ClickTime ending support for TLS 1.0 and 1.1

In order to keep ClickTime working smoothly, securely and to add new functionality, it becomes necessary to stop supporting old technology. Following in the footsteps of Google, Apple, Mozilla and Microsoft, we are going to end support for TLS (Transport Layer Security) versions 1.0 and 1.1 on September 15, 2020. 

All supported browsers and operating systems already support TLS 1.2 so this should not affect any individual person’s ability to access and use ClickTime’s web and mobile apps. It’s possible, however, that some integrations or third-party solutions that interact with ClickTime in an automated fashion using our REST API, SOAP API or Excel Linking features may have been built on outdated technology that doesn’t support modern security standards.

In advance of September 15, we will implement a 48-hour test deprecation starting at 10am Pacific Time (4pm GMT) on July 28th, 2020 and running through 10am (4pm GMT) on July 30th, 2020. This test is about three weeks away.

In order to keep your ClickTime integrations working without interruption, please test your integrations during the 48-hour test window to ensure your software supports TLS 1.2. You can continue reading for more information:

Why are we deprecating TLS 1.0 and 1.1?

We are deprecating TLS 1.0 and 1.1 to ensure ClickTime supports our customers and partners with safe and secure communication protocols. The use of TLS 1.2 is a recommended security best practice that provides a higher degree of privacy and data integrity over previous versions and to maintain compliance with the latest industry standards.

What you should know?

Transport Layer Security (TLS) is a cryptographic protocol used to establish a secure communications channel between two systems. It is used to authenticate one or both systems and protect the confidentiality and integrity of information that passes between them. TLS 1.2 was published in 2008 to replace version 1.0 (published in 1999) and version 1.1 (published in 2006).

How can I track whether I’m impacted by this or not?

Check internally if there are any integrations using older versions. We also highly recommend using your integrations during the 48-hour test deprecation window. If the integrations work normally, then you’re ok. If your integration doesn’t work during the 48-hour test deprecation window, your integration or the system on which it’s running will need to get updated to maintain compliance with the latest industry standards and keep functioning after September 15.

What happens if my system doesn’t support TLS 1.2 and I don’t upgrade them?

If any of your integrations still require an older TLS version after these old versions are deprecated in September then those integrations won’t be able to connect to ClickTime.

If you have any additional questions, please contact ClickTime Support.

The ClickTime Team

ClickTime Login and Load Issues [Resolved] – November 18 2019

12:10 pm – ClickTime has resolved the performance issue that prevented certain users from accessing ClickTime. Application response time has returned to normal. We apologize for any inconvenience you may have experienced. Please email support@clicktime.com if you have questions or additional issues of any nature. Thank you for your understanding.

11:40 am – While performance times are improving, ClickTime is continuing to investigate an issue that appears to prevent certain users from logging into ClickTime. We appreciate your understanding and will continue posting updates on this topic as soon as we know more.

11:00 am – ClickTime is investigating a potential issue that may impact load times and logging in. Our team is working to understand and resolve this as soon as possible.