Documentation

InfluxDB Clustered

Create a management token

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, 2025-10-12T00: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 in double quotes "".
influxctl management create \
  --expires-at 
RFC3339_EXPIRATION
 \
  --description "
TOKEN_DESCRIPTION
"

Replace the following:

  • RFC3339_EXPIRATION: An RFC3339 date string to expire the token at–for example, 2025-10-12T00: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.

tokens

Was this page helpful?

Thank you for your feedback!

© 2025 InfluxData, Inc.

What is your InfluxDB cluster URL?

Enter your InfluxDB cluster URL and we’ll update code examples for you.

Enter cluster URL

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2