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: 

Custom url callback scheme

‎11-25-2015 13:27

‎11-25-2015 13:27

I found that the Callback URL becomes required in "Edit the Application", (I remember it used to be optional.) and the redirect_uri I specify for OAuth 2 need to match this URL. Will the old OAuth 1 also be affected by this change?

Best Answer
Labels:
0 Votes
1 REPLY 1

‎11-25-2015 14:13

‎11-25-2015 14:13

OAuth 1.0a allows your application to specify a callback URI as part of the start of the authorization process.

 

OAuth 2.0 requires the redirect URI be specified separately from the authorization process, as there is no pre-authorization request.

 

The OAuth 2.0 requirement will not affect your OAuth 1.0a application unless your application does not specify a callback URI with OAuth 1.0a and relies on the URI being specified in your application settings. In that case, just be sure to leave your OAuth 1.0a callback URI as the first URI listed.

Best Answer