I'd like to set a dynamic redirect_uri to include the current user's ID, but if I send anything that doesn't match the dashboard's URI, I get an error.
Beyond that, when I do get a response by exluding the redirect_uri from the post, the response comes back as a url with a hash, not a query string or post.
This is the response I'm getting on the redirect_uri:
http://www.url.com/fitness/authorize/1#scope=settings+activity+profile&user_id={user}&token_type=Bearer&expires_in=2569304&access_token={token}I've tried adding a '?' to see if it will change the value, but it does not.
I see the use mentioned in the RFC at http://tools.ietf.org/html/rfc6749#section-4.2.2, but I guess I'm not sure what I'm supposed to do with the response?
I'm using Slim framework for PHP (not my choice).
EDIT:
I just read this thread and I get that I should be passing the user ID in the state parameter. Makes sense now.
Answered! Go to the Best Answer.
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
The Implicit Grant Flow (meants for browser and client-based apps) uses the URL fragment (#). Browsers do not send URL fragments to the server.
Web server apps should use the Authorization Code Grant Flow to get a redirect with URL parameters.
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
The Implicit Grant Flow (meants for browser and client-based apps) uses the URL fragment (#). Browsers do not send URL fragments to the server.
Web server apps should use the Authorization Code Grant Flow to get a redirect with URL parameters.
Best Answer