influx auth inactive
influx auth inactive command inactivates an API token in InfluxDB.
Inactive tokens do not authorize access to InfluxDB.
To temporarily disable client access to InfluxDB, inactivate the authentication token the client is using rather than delete the token. If you delete the token, you have to generate a new token and update the client with the new token. By setting a token to inactive, you can activate the token to grant the client access without having to modify the client.
influx auth inactive [flags]
|Flag||Description||Input type||Maps to ?|
|CLI configuration to use for command||string|
|Path to ||string|
|Help for the |
|Hide table headers (default |
|HTTP address of InfluxDB (default ||string|
|Inspect communication with InfluxDB servers.||string|
|(Required) API token ID||string|
|Output data as JSON (default |
|Skip TLS certificate verification|
The examples below assume your InfluxDB host, organization, and token are
provided by either the active
influx CLI configuration or by environment variables (
If you do not have a CLI configuration set up or the environment variables set, include these required credentials for each command with the following flags:
--host: InfluxDB host
--org-id: InfluxDB organization name or ID
-t, --token: InfluxDB API token
Inactivate an API token
influx auth inactive --id 06c86c40a9f36000
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 and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.