Getting an error when server support TLS 1.2

[hsalbi]

I am getting the following error when the server does not support TLS 1.0 and 1.1 

The client and Server cannot communicate,because they do not possess a common algorithm

If I re enable the support for TLS 1.0, I dont see the error anymore but we fail the PCI scan?

Any help?

Thanks, 

[GordonFitbit]

Hi @hsalbi,

Which API calls are failing for you?  Have you tried TLS 1.2?

[hsalbi]

Hi Godon, 

I am accessing the web API to get the authorization token for the user.

https://api.fitbit.com/oauth2/token

TLS 1.2 is not working as well.

[GordonFitbit]

Hi @hsalbi.  What programming language is your application written with? 

Have you tried the OAuth 2.0 Tutorial to determine if you can successfully connect?  This will remove your application from the environment and confirm if the problem is with the Fitbit service or your application communicating with Fitbit.  

The OAuth 2.0 Tutorial can be found here.  Or you can access it from dev.fitbit.com within your application's configuration.  We will fill in parameters automatically based on the information in your application's settings.

[hsalbi]

Hi Gordon,

We are using MVC with C#  .net 4.5.  everything works fine if window server support TLS 1.0 but it breaks when the server stop supporting TLS 1.0 force the use of TLS 1.2

Does Fitbit support TLS 1.2?

I will try the tutorial but I don't think I can enforce the use of TLS 1.2.

Thanks,