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: 

OAuth 2.0 Callback URL Matching Patterns

‎11-06-2015 06:26

‎11-06-2015 06:26

Fitbit Team, we would like to know if there is way to use URL patterns when configuring the Callback URL in each of the apps.

 

Our problem is that we currently have a lot of different URLs that are used to access our Web application. Having to configure each one of the URLs leads to maintanibility issues and potential problems when URL is not included.

 

Is there any support for URLs patterns that could avoid configuring every single URL?

 

For example, the following pattern "https://*.domain.com/fitbit/oauth2callback" would support:

https://www.domain.com/fitbit/oauth2callback

https://client1.domain.com/fitbit/oauth2callback

https://www.client1.domain.com/fitbit/oauth2callback

https://client2.domain.com/fitbit/oauth2callback

https://www.client2.domain.com/fitbit/oauth2callback

 

 

Best Answer
Labels:
0 Votes
1 REPLY 1

‎11-06-2015 11:10

‎11-06-2015 11:10

Callback URIs will need to be explicitly defined.

 

Best Answer
0 Votes