Documentation

Create a management token

Limited availability

InfluxDB Clustered is currently 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.

By default, management tokens are short-lived tokens issued by an OAuth provider that grant a specific user administrative access to your InfluxDB 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 OAuth provider.

For automation use cases only

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

InfluxDB Clustered requires at least one user associated with your cluster and authorized through OAuth to manually create a management token.

  1. If you haven’t already, download and install the influxctl CLI.

  2. Use the influxctl management create command to manually create a management token. Provide the following:

    • Optional: the --expires-at flag with an RFC3339 date string that defines the token expiration date and time–for example, 2024-04-18T00:00:00Z. If expiration isn’t set, the token does not expire until revoked.
    • Optional: the --description flag with a description for the management token.
influxctl management create \
  --expire-at 
RFC3339_EXPIRATION
\
--description
TOKEN_DESCRIPTION

Replace the following:

  • RFC3339_EXPIRATION: An RFC3339 date string to expire the token at–for example, 2024-04-18T00:00:00Z.
  • TOKEN_DESCRIPTION: Management token description.

The output contains the management token string.

Store secure tokens in a secret store

Management token strings are returned only on token creation. We recommend storing database tokens in a secure secret store. For example, see how to authenticate Telegraf using tokens in your OS secret store.


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: