Documentation

influx v1 auth set-active

Not supported in InfluxDB Cloud

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

The influx v1 auth set-active command activates an authorization in the InfluxDB 1.x compatibility API. Only active authorizations grant access to InfluxDB.

Usage

influx v1 auth set-active [flags]

Flags

FlagDescriptionInput typeMaps to ?
-c--active-configConfig name to use for commandstring$INFLUX_ACTIVE_CONFIG
--configs-pathPath to the influx CLI configurations (default: ~/.influxdbv2/configs)string$INFLUX_CONFIGS_PATH
-h--helpHelp for the set-active command
--hide-headersHide the table headers (default: false)$INFLUX_HIDE_HEADERS
--host(Required) HTTP address of InfluxDBstring$INFLUX_HOST
-i--idAuthorization IDstring
--jsonOutput data as JSON (default: false)$INFLUX_OUTPUT_JSON
--skip-verifySkip TLS certificate verificationINFLUX_SKIP_VERIFY
-t--tokenAPI tokenstring$INFLUX_TOKEN
--usernameAuthorization usernamestring$INFLUX_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
Activate a v1 authorization
influx v1 auth set-active --id 00xX00o0X001

Was this page helpful?

Thank you for your feedback!


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:

InfluxDB Cloud powered by TSM