-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't get authentication working #28
Comments
I've been looking into this the past few days and I think I found out a possible reason; check out this post on the Fitbit dev forums which explains a change they made where new credentials are created for a user upon every oauth login flow- if you are storing and reusing the tokens returned by Fitbit but allowing (or forcing) the user to relogin through the OAuth flow then the tokens you have stored may be out of sync with the latest returned by the service. I'm in the process of testing out this theory on the client application (which is currently broken) and I'll update this issue with more info when I have it. |
Hey Zachery, I tried to access the API without re-authorizing but I'm still having the I noticed when using the API explorer on the FB website, they include stuff TIA, SUDO Labs | Zuluworks.com | ThreePoint.io | CheckRide.io Cell: 804.690.5896On Wed, May 7, 2014 at 1:23 PM, Zachery Moneypenny <notifications@github.com
|
I figured out the fix for what I was seeing with the same error in the fitgem-client project (see this issue/commit for more info). You may want top sniff the request/response to the api.fitbit.com endpoint and compare the oauth user tokens returned by the login redirect to what you're sending with the API request to make sure they match. |
To answer your other question; the oauth library takes care of generating the oauth_signature/nonce, etc. |
Zachery, -Peter SUDO Labs | Zuluworks.com | ThreePoint.io | CheckRide.io Cell: 804.690.5896On Thu, May 8, 2014 at 3:57 PM, Zachery Moneypenny <notifications@github.com
|
Hi,
Thanks so much for putting this gem out there. I'm trying to integrate with the FB api and your work has made it much simpler!
I'm having the following issue. The initial oauth authentication seems to be working just fine. I receive and store the oauth token and secret with the user when they authorize my app. Setting up your client seems to go smoothly, however when I invoke one of the API methods, I get the following. What am I doing wrong?:
=> {"errors"=>
[{"errorType"=>"oauth",
"fieldName"=>"oauth_access_token",
"message"=>
"Invalid signature or token '/WXdJVXivN3OuIXl16I7ZOAHpUQ=' or token '76db9d2bf0201e0d6f91f302d5a118e4'"}],
"success"=>false}
The text was updated successfully, but these errors were encountered: