influx v1 auth
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.
The influx v1 auth subcommands provide authorization management for the
InfluxDB 1.x compatibility API.
InfluxDB 2.9 uses API tokens to authorize API requests. The 1.x compatibility API lets clients authenticate with InfluxDB 2.9 using the InfluxDB 1.x convention of username and password.
v1-compatible authorizations are separate from the credentials used to log into the InfluxDB user interface.
Usage
influx v1 auth [flags]
influx v1 auth [command]Command aliases
auth, authorization
Commands
| Command | Description |
|---|---|
| create | Create authorization |
| delete | Delete authorization |
| list | List authorizations |
| set-active | Activate an authorization |
| set-inactive | Deactivate an authorization |
| set-password | Set a password for an existing authorization |
Flags
| Flag | Description | |
|---|---|---|
-h | --help | Help for the v1 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.