Manage secrets
API token hashing is enabled by default in InfluxDB OSS 2.9.0
Stronger token security: tokens are stored as hashes on disk, so a copy of the database file doesn’t expose usable tokens. Existing tokens are hashed on first startup and the original strings can’t be recovered afterward — capture any plaintext tokens you still need before you upgrade.
For more information, see Token hashing.
Secrets are key-value pairs that contain sensitive information you want to control access to, such as API keys, passwords, or certificates. There are two options for storing secrets with InfluxDB:
- By default, secrets are Base64-encoded and stored in the InfluxDB embedded key value store, BoltDB.
- You can also set up a Vault server to store secrets. For details, see Store secrets in Vault.
Add secrets
Add secrets using the influx CLI or the InfluxDB API.
View secret keys
View secret keys using the influx CLI or the InfluxDB API.
Update secrets
Update secrets using the influx CLI or the InfluxDB API.
Delete secrets
Delete secrets using the influx CLI or the InfluxDB API.
Use secrets
Use secrets in a query with Flux.
Store secrets in Vault
Use Vault as an InfluxDB secret store and manage secrets through the in InfluxDB API.
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB OSS v2 and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.