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: 

Not asking for login details while calling authorization URL

‎11-16-2015 01:16

‎11-16-2015 01:16

Hi,

I am trying with OAuth 2.0 for both Authorization Code Grant Flow and Implicit Grant Flow.

I provided all the details and tried hitting authorization URL. For the first time it asked me for user details and gave me a response i.e. code or access token. Then i again tried hitting authorization URL for another user, but the login page didnt show up. I had to delete my browser cookies and hit the authorization URL for it to work. 

Is this the way the authorization URL works ? Am i suppose to delete the cookies everytime before i hit authorize URL for new user ?

 

Thanks in advance.

Best Answer
Labels:
0 Votes
1 REPLY 1

‎11-16-2015 11:20

‎11-16-2015 11:20

@vrushankd wrote:

Hi,

I am trying with OAuth 2.0 for both Authorization Code Grant Flow and Implicit Grant Flow.

I provided all the details and tried hitting authorization URL. For the first time it asked me for user details and gave me a response i.e. code or access token. Then i again tried hitting authorization URL for another user, but the login page didnt show up. I had to delete my browser cookies and hit the authorization URL for it to work. 

Is this the way the authorization URL works ? Am i suppose to delete the cookies everytime before i hit authorize URL for new user ?

 

Thanks in advance.

The reason you are seeing this behavior is that once the original user logins to Fitbit.com to give consent to your application, they stay logged in on fitbit.com. The next time you prompt for the exact same permissions from the same logged in user, we automatically redirect them back to your app since they've previously granted permission and no additional consent is required.

 

You can use the "prompt" parameter on the authorization URL to force the user to login. Please see:

https://dev.fitbit.com/docs/oauth2/#authorization-page

Best Answer