Manage management tokens

Management tokens grant permission to perform administrative actions such as managing users, databases, and database tokens in your InfluxDB Cloud Dedicated cluster.

Management tokens do not grant permissions to write or query time series data in your InfluxDB Cloud Dedicated cluster.

To grant write or query permissions, use management tokens to create database tokens.

By default, management tokens are short-lived tokens issued by an OAuth2 identity provider that grant a specific user administrative access to your InfluxDB Cloud Dedicated cluster. However, for automation purposes, you can manually create management tokens that authenticate directly with your InfluxDB Cluster and do not require human interaction with your identity provider.

For automation use cases only

The tools outlined below are meant for automation use cases and should not be used to circumvent your identity provider. Take great care when manually creating and using management tokens.

InfluxDB Cloud Dedicated requires at least one user associated with your cluster and authorized through your OAuth2 identity provider to manually create a management token.

Use a management token

Use management tokens to automate authorization for the influxctl CLI:

  1. Create a management token and securely store the output token value. You’ll use it in the next step.
  2. On the machine where the influxctl CLI is to be automated, update your influxctl connection profile by assigning the mgmt_token setting to the token string from the preceding step.
  name = "default"
  product = "dedicated"
  account_id = "
cluster_id = "
mgmt_token = "

Replace the following:

  • ACCOUNT_ID: InfluxDB Cloud Dedicated account ID
  • CLUSTER_ID: InfluxDB Cloud Dedicated cluster ID
  • MANAGEMENT_TOKEN: Management token string

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: