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: 

Client Secret missing in my registered Application

‎01-29-2018 04:34

‎01-29-2018 04:34

I have a problem with an Application I registered yesterday - the Client Secret field remains empty .

 

I registered an Application on https://dev.fitbit.com/apps with OAuth 2.0 Application Type "Server" . I understand this field is required for the Authorization Code Grant flow.

I can see all the other fields and I also have an option to Reset Client Secret (which does not seem to do anything)

 

Is there anything special that needs to be done / configured to get this Client Secret field visible? 

 

Thank you!

Adam

 

 

Best Answer
0 Votes
2 REPLIES 2

‎01-30-2018 13:22

‎01-30-2018 13:22

There is an issue with the secret generation right now, please add a comment in this thread.

Best Answer
0 Votes

‎01-30-2018 13:23

In response to SunsetRunner

‎01-30-2018 13:23

Moved to the Web API forum.

Best Answer
0 Votes