Deprecating Support for TLS 1.0 and TLS 1.1 on May 18, 2020

[Gordon-C]

As Fitbit continues to improve the security and performance of our infrastructure for accessing Fitbit user data, we've made the decision to deprecate support for TLS 1.0 and TLS 1.1.  This decision follows suit with the Internet Engineering Task Force and Cloudflare, our cloud service provider.  Fitbit will continue to support TLS 1.2 which has been in existence since 2008.  According to the wiki page "Comparison of TLS implementations", most current operating systems and SSL libraries are now supporting TLS 1.2 as the default standard.  Therefore, we believe there will be minimal impact to our customers.

On May 18, 2020, we will deprecate TLS 1.0 and TLS 1.1.  In addition, we will add support for TLS 1.3.  Please confirm with your IT department that your applications and services, which communicate with Fitbit, are configured to use TLS 1.2 or TLS 1.3.

The Fitbit API Support team will be happy to answer any questions about this information in the forums.

Best regards,

Fitbit API Support team

[goaliejd]

Is there a way to disable this completely within an app (rather than it just being deprecated)?

[Gordon-C]

Hi @goaliejd 

Fitbit has disabled TLS 1.0 and 1.1 on our side.  If you want to disable it on your side, then I would recommend talking with your IT / network person for help.   

Gordon

[goaliejd]

Thanks Gordon