Documentation

influx v1 auth set-inactive

Not supported in InfluxDB Cloud

InfluxDB Cloud does not support InfluxDB 1.x compatible authorizations. Using the influx v1 auth set-inactive command with InfluxDB Cloud will result in an error. To authenticate with InfluxDB Cloud, use InfluxDB token authentication.

The influx v1 auth set-inactive command deactivates an authorization in the InfluxDB 1.x compatibility API. Inactive authorizations do not grant access to InfluxDB.

Usage

influx v1 auth set-inactive [flags]

Flags

FlagDescriptionInput typeMaps to ?
-c--active-configConfig name to use for commandstringINFLUX_ACTIVE_CONFIG
--configs-pathPath to the influx CLI configurations (default: ~/.influxdbv2/configs)stringINFLUX_CONFIGS_PATH
-h--helpHelp for the set-inactive command
--hide-headersHide the table headers (default: false)INFLUX_HIDE_HEADERS
--hostHTTP address of InfluxDBstringINFLUX_HOST
-i--id(Required) Authorization IDstring
--jsonOutput data as JSON (default: false)INFLUX_OUTPUT_JSON
--skip-verifySkip TLS certificate verificationINFLUX_SKIP_VERIFY
-t--tokenAPI tokenstringINFLUX_TOKEN
--usernameAuthorization usernamestringINFLUX_USERNAME

Examples

Authentication credentials

The examples below assume your InfluxDB host, organization, and token are provided by either the active influx CLI configuration or by environment variables (INFLUX_HOST, INFLUX_ORG, and INFLUX_TOKEN). 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
  • -o, --org or --org-id: InfluxDB organization name or ID
  • -t, --token: InfluxDB API token
Deactivate a v1 authorization
influx v1 auth set-inactive --id 00xX00o0X001

Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following:

State of the InfluxDB Cloud Serverless documentation

InfluxDB Cloud Serverless documentation is a work in progress.

The new documentation for InfluxDB Cloud Serverless is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.

InfluxDB Cloud powered by TSM