Delete secrets
This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.
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.
Delete secrets using the influx command line interface (CLI) or the InfluxDB API.
Delete a secret using the influx CLI
Use the influx secret delete command
to delete a secret key-value pair from your organization.
Provide the secret key to delete with the -k or --key flag.
# Syntax
influx secret delete -k <secret-key>
# Example
influx secret delete -k fooDelete secrets using the InfluxDB API
Use the POST request method and the orgs/{orgID}/secrets/delete API endpoint
to delete one or more secrets.
Include the following:
- Your organization ID in the request URL
- Your API token in the
Authorizationheader - An array of secret keys to delete in the request body
curl --request GET http://localhost:8086/api/v2/orgs/<org-id>/secrets/delete \
--header 'Authorization: Token YOURAUTHTOKEN' \
--data '{
"secrets": [
"<secret-key>"
]
}'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.