Documentation

influxctl management revoke

The influxctl management revoke command revokes management token access to your InfluxDB cluster. This operation cannot be undone.

Revoked tokens are included when listing tokens

Revoked tokens still appear when listing management tokens, but they are no longer valid for any operations.

Usage

influxctl management revoke [flags] <TOKEN_ID>[ ... TOKEN_ID_N]
  • Copy
  • Fill window

Arguments

ArgumentDescription
TOKEN_IDToken ID(s) to revoke access from (space-delimit multiple IDs)

Flags

FlagDescription
--forceDo not prompt for confirmation to revoke
-h--helpOutput command help

Examples

In the examples below, replace the following:

  • TOKEN_ID*: Token ID to revoke access from.

Revoke access from a management token

influxctl management revoke 
TOKEN_ID
  • Copy
  • Fill window

Revoke access from multiple management tokens

influxctl management revoke 
TOKEN_ID_1
TOKEN_ID_2
  • Copy
  • Fill window

Revoke access from a token and skip confirmation

influxctl management revoke --force 
TOKEN_ID
  • Copy
  • Fill window

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.

Read more

InfluxDB 3 Core and Enterprise are now in Beta

InfluxDB 3 Core and Enterprise are now available for beta testing, available under MIT or Apache 2 license.

InfluxDB 3 Core is a high-speed, recent-data engine that collects and processes data in real-time, while persisting it to local disk or object storage. InfluxDB 3 Enterprise is a commercial product that builds on Core’s foundation, adding high availability, read replicas, enhanced security, and data compaction for faster queries. A free tier of InfluxDB 3 Enterprise will also be available for at-home, non-commercial use for hobbyists to get the full historical time series database set of capabilities.

For more information, check out: