06-23-2017 03:43 - edited 06-25-2017 17:27
06-23-2017 03:43 - edited 06-25-2017 17:27
Hi all
Currently we are implementing Fitbit Authentication in a product which was developed long ago. They have used HttpClient3.x(commons-httpclient).
When we implemented using HttpClient4.x(HttpComponents), everything works like charm.
But the customer wants to try with older version itself.
We tried to implement the same using HttpClient3.x(commons-httpclient) .Have implemented necessary proxy handling process also.
Endpoint we used is https://www.fitbit.com/oauth2/authorize in both the process but we are getting the following error in the response only when we use HttpClient3.x(commons-httpclient).
The owner of this website (www.fitbit.com) has banned your access based on your browser's signature
Is there any restriction of using HttpClient3.x(commons-httpclient) for performing Fitbit Authorization?
or
Does Fitbit Website requires preemptive authentication for OAuth, for which we cannot use HttpClient 3.0.x?. But details of requiring preemptive authentication is nowhere mentioned as far as i have gone through the api documents.
Can you please help us in investigation what was wrong