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: 

FitBit WebAPI oAuth as an external auth provider

‎08-14-2018 04:31 - edited ‎08-14-2018 04:32

‎08-14-2018 04:31 - edited ‎08-14-2018 04:32

Hello. I have just started building a website that uses webserver-to-Fitbit API Authorization Code Grant Flow. This is my first time using oAuth but so far so good with WebAPI access.

 

What I haven't worked out is if I can use Fitbit oAuth as an authentication provider for our website, similar to how many sites and apps allow you to sign in with Google or Facebook accounts (which I believe is an application of oAuth) as opposed to users having to create new accounts. I am using ASP.NET Core which allows 3rd party authentication providers to be pretty much plugged in.

 

I haven't seen any reference to this in any documentation, so I am guessing no and if no is this a technical limitation or a terms of service issue? Maybe I have misunderstood the extent of oAuths use.

 

Thanks

Michael

Best Answer
Labels:
0 Votes
0 REPLIES 0