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: 

Storing sensitive information like API keys and secrets

‎06-30-2020 05:51

‎06-30-2020 05:51

Hey guys!

 

On our project we're needing to connect to an external API through the OAuth component, but we're having to hardcode the API keys, secrets and even refresh tokens in order to make it work.

 

Is there a way to store this sensitive information somewhere else so that it's fully secured against any threat?

Best Answer
0 Votes
1 REPLY 1

‎07-02-2020 16:59

‎07-02-2020 16:59

Hello,

I know little about these things, but it seems that the Crypto API might be what you are looking for. As far as where to store it, I guess that depends on where you are using it, but my assumption would be that the most secure place would be the companion app. The API uses CBOR to send data from the companion to the watch.

 

Best Answer
0 Votes