Documentation

influx v1 auth set-inactive

This page documents an earlier version of InfluxDB. InfluxDB v2.7 is the latest stable version. View this page in the v2.7 documentation.

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!


Set your InfluxDB URL

Introducing InfluxDB 3.0

The new core of InfluxDB built with Rust and Apache Arrow. Available today in InfluxDB Cloud Dedicated.

Learn more

State of the InfluxDB Cloud Serverless documentation

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.