Redirect Loop

[Bob Weigel]

Not necessarly an issue, but may be worth documenting here. I encountered a problem with fitbit-js that seems to be an issue with the Fitbit API: https://community.fitbit.com/t5/Third-Party-Integrations/Stuck-in-Deny-Allow-loop-when-trying-to-give-access-using-OAuth/m-p/814536

Message I wrote is repeated below.

---

I did

git clone https://github.com/smurthas/fitbit-js.git
cd fitbit-js
npm install
cd example
node test.js [Consumer Key] [Consumer Secret]

I have the callback URL set to http://localhost:8553/ (also tried http://localhost:8553/getStuff)

I opened http://localhost:8553/ in a Chrome when I was logged-in in another tab. I sent to https://www.fitbit.com/oauth/authorize?oauth_token=... was given the Deny/Accept option. I clicked Accept, was sent to http://localhost:8553/?oauth_token=...&oauth_verifier=... which then sent a 302 redirect back to https://www.fitbit.com/oauth/authorize?oauth_token=...

I tried this in Safari and Firefox - I have never logged into Fitbit in these accounts. I also tried clearing the cache and got the same result. Same when using incognito mode.

[Simon Murtha Smith]

@rweigel Are you still having this issue?

If so, are you using OAuth 1 or 2? And would you please post a screenshot of you application configuration, e.g.

[Bob Weigel]

@smurthas - I don't have the issue now. Thanks. I have it working with the same settings as in your image except with an application type of personal.

I may have had a trailing slash in the callback URL when I tried the first time. I just tried with and without the trailing slash and did not have the problem.