ClickTime Scheduled Maintenance

The ClickTime system will be undergoing emergency maintenance on Sunday, January 10 at 12:00 noon Pacific Standard Time (GMT -08:00).

This maintenance window will last for three (3) hours, with service resuming at 3:00pm Pacific Standard Time (GMT -08:00). During this time, the ClickTime system will be periodically unavailable or respond more slowly than usual.

Explanation: As a result of network performance issues identified today, Saturday January 9, we are taking advantage of the weekend to accelerate equipment upgrades on our network which had been planned for February. The availability and security of the ClickTime system is our top priority. We sincerely apologize if this maintenance causes you any inconvenience.

As always, we welcome questions or concerns at support@clicktime.com or follow @clicktime on Twitter.

TLS 1.0 and 1.1 Not Supported as of September 15, 2020

As previously announced, we will no longer support TLS (Transport Layer Security) versions 1.0 and 1.1 starting 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.

For more information regarding TLS please see the following:

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?

If your integration stops functioning after September 15, 2020, your integration or the system on which it’s running will need to get updated to maintain compliance with the latest industry standards.

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 on September 15, 2020, those integrations won’t be able to connect to ClickTime.

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

The ClickTime Team

TLS 1.0/1.1 Deprecation Test Starts Today

As previously announced we are beginning a 48-hour TLS deprecation test starting at 10am Pacific Time (4pm GMT) today, July 28th, 2020, and it will run through 10am (4pm GMT) on July 30th, 2020. During this time, we will stop supporting TLS (Transport Layer Security) versions 1.0 and 1.1. 

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.

Please test your ClickTime integrations during the 48-hour test window to ensure your software supports TLS 1.2.

For more information regarding TLS please see the following:

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?

We 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, 2020.

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 on September 15, 2020, those integrations won’t be able to connect to ClickTime.

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

The ClickTime Team

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

Ending Support for the RC4 Cipher

In order to keep ClickTime working smoothly, securely and to add new functionality, it becomes necessary to stop supporting legacy technology. Following in the footsteps of Google, Mozilla and Microsoft, we are announcing the end-of-support for the RC4 cipher as of April 25, 2016. Newer and more secure ciphers are supported by all modern supported browsers and operating systems, so this shouldn’t effect our customers but we want to be transparent with changes such as these.

Why is this happening?

  • The RC4 cipher is less secure. Multiple security vulnerabilities were discovered over the years and we want to make sure our customers' data is safe.
  • Our customers are using modern browsers and operating systems (not Windows XP). Less than 0.3% of people in ClickTime use an old browser and old operating system, such as IE 8 and Windows XP.

What does this mean to me?

  • This should not affect you, as these changes only impact older browsers such as IE8 running on Windows XP. But, after April 25, 2016, people who attempt to sign in to ClickTime with an old browser and operating system, will get a browser error about not being able to load the page.

How can I get more information?

ClickTime Support is always available to answer any questions you may have about this change. If you have further questions, please let us know.

Changes for your Whitelist

Some security-conscious companies utilize explicit whitelists of web sites in order for you to access web applications such as ClickTime. If this describes your company, please be aware of a couple of new web site addresses that we’ll be utilizing in forthcoming updates.

Some security-conscious companies utilize explicit whitelists of web sites in order for you to access web applications such as ClickTime. If this describes your company, please be aware of the following new web site addresses (a.k.a. URLs) that we'll be utilizing in forthcoming updates:

  • help.clicktime.com
  • cdn.clickstatic.com

Please add these addresses to your whitelist or other web filters in order to keep using ClickTime as usual. We expect to start using help.clicktime.com as soon as September 22. The cdn.clickstatic.com URL is planned for implementation the week of October 5. If you have any questions, please contact ClickTime Support.