[GH-ISSUE #686] Docs request: how to prevent secrets from leaving local storage wrt. sync. #239

Closed
opened 2026-03-16 14:10:36 +03:00 by kerem · 3 comments
Owner

Originally created by @neverendingqs on GitHub (Mar 19, 2020).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/686

Is your feature request related to a problem? Please describe.
I am not sure how I should set up sync to prevent secrets (e.g. OAuth 2.0 access tokens) from leaving local storage.

Describe the solution you'd like
Help text or documentation describing what exactly is synced and/or suggestions for how to manage secrets and syncing.

Describe alternatives you've considered
I think using Environments to store secrets and referencing them in request collections might be the way to go?

Additional context
N/A

Originally created by @neverendingqs on GitHub (Mar 19, 2020). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/686 **Is your feature request related to a problem? Please describe.** I am not sure how I should set up sync to prevent secrets (e.g. OAuth 2.0 access tokens) from leaving local storage. **Describe the solution you'd like** Help text or documentation describing what exactly is synced and/or suggestions for how to manage secrets and syncing. **Describe alternatives you've considered** I think using Environments to store secrets and referencing them in request collections might be the way to go? **Additional context** N/A
kerem closed this issue 2026-03-16 14:10:41 +03:00
Author
Owner

@liyasthomas commented on GitHub (Mar 19, 2020):

Synced sections are:

  • History
  • Collections
  • Environments
  • Notes

Secrets including 0Auth key or access tokens are synced with localStorage only.

<!-- gh-comment-id:601242079 --> @liyasthomas commented on GitHub (Mar 19, 2020): Synced sections are: - History - Collections - Environments - Notes Secrets including 0Auth key or access tokens are synced with `localStorage` only.
Author
Owner

@sachaventura2 commented on GitHub (Apr 21, 2022):

Hi there,

What are the best practices to store API keys, passwords etc. in Team collections?
Coming from Postman, we usually store them in the environment, as "current values" which are only stored locally.

Secrets including 0Auth key or access tokens are synced with localStorage only.

How are 0Auth keys and access token identified as such?

Thanks for clarifying!

<!-- gh-comment-id:1104617791 --> @sachaventura2 commented on GitHub (Apr 21, 2022): Hi there, What are the best practices to store API keys, passwords etc. in Team collections? Coming from Postman, we usually store them in the environment, as "current values" which are only stored locally. > Secrets including 0Auth key or access tokens are synced with localStorage only. How are 0Auth keys and access token identified as such? Thanks for clarifying!
Author
Owner

@dakujem commented on GitHub (Oct 5, 2023):

This should not have been closed. There are values we never want to save anywhere, neither sync. So how do we do this? I'm searching like crazy, but can't find anything.

Trivial example: I want to authenticate to an API, but I do not wish to store/sync the credentials anywhere. How to?

@liyasthomas Thanks.

<!-- gh-comment-id:1748245746 --> @dakujem commented on GitHub (Oct 5, 2023): This should not have been closed. There are values we **never** want to save anywhere, neither sync. So how do we do this? I'm searching like crazy, but can't find anything. Trivial example: I want to authenticate to an API, but I do not wish to store/sync the credentials anywhere. How to? @liyasthomas Thanks.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#239
No description provided.