Documentation

Manage tokens

InfluxDB uses token authentication to authorize access to data in your InfluxDB cluster. With InfluxDB Clustered, there are two types of tokens:

Database tokens

Database tokens grant read and write permissions to one or more databases and allows for actions like writing and querying data.

All read and write actions performed against time series data in your InfluxDB cluster must be authorized using a token.

Management tokens

Management tokens grant permission to perform administrative actions such as managing users, databases, and database tokens. Management tokens allow clients, such as the influxctl CLI, to perform administrative actions.

Store secure tokens in a secret store

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!


New in InfluxDB 3.6

Key enhancements in InfluxDB 3.6 and the InfluxDB 3 Explorer 1.4.

See the Blog Post

InfluxDB 3.6 is now available for both Core and Enterprise. This release introduces the 1.4 update to InfluxDB 3 Explorer, featuring the beta launch of Ask AI, along with new capabilities for simple startup and expanded functionality in the Processing Engine.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 2026, 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