influx auth
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.
The influx auth command and its subcommands manage API tokens in InfluxDB.
Usage
influx auth [flags]
influx auth [command]Command aliases
auth, authorization
Subcommands
| Subcommand | Description |
|---|---|
| active | Activate API token |
| create | Create API token |
| delete | Delete API token |
| list | List API tokens |
| inactive | Inactivate API token |
Flags
| Flag | Description | |
|---|---|---|
-h | --help | Help for the auth command |
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.