help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Does Fitbit redirect to the callback if the user has given access before?

‎04-22-2016 17:07 - edited ‎04-22-2016 17:12

‎04-22-2016 17:07 - edited ‎04-22-2016 17:12

With Oauth1 if a user has given permission to the app and they go to the authorization url again then they are given the opportunity to Accept or Deny. If they Accept it goes to the callback url, if they Deny then it goes to the callback url and also removes the given permission. 

 

Is this behavior different for Oauth2? When a user who already has permission goes to the authorlization url again (with a new code) does Fitbit simply redirect to the callback url? I was expecting to see the Authorization page again. 

 

Thanks 

 

EDIT: I see there is a "prompt" option I can specify. Based on my description if I was to keep the behavior the same I need to set the prompt to "consent" ? 

Best Answer
Labels:
0 Votes
0 REPLIES 0