chronoctl token

The token command reads a private token file, generates and signs the nonce, and then returns an expiring token to be used in the Authorization header. For example:

Authorization: CHRONOGRAF-SHA256 <returned-expiring-token>


chronoctl token [flags]


FlagDescriptionEnv. Variable
-h--helpOutput command help
--chronograf-urlChronograf’s URL (default is http://localhost:8888)CHRONOGRAF_URL
-k--skip-verifySkip TLS certification verification
--priv-key-filePrivate key file location for superadmin token authenticationPRIV_KEY_FILE


The following example uses the RSA key used when started the Chronograf server and returns an expiring token that can be used to gain superadmin access to Chronograf.

The private key must correspond to the public key used when starting the Chronograf server.

chronoctl token --priv-key-file /path/to/chronograf-rsa

Was this page helpful?

Thank you for your feedback!

Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is 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.

Learn more
Contact InfluxData Sales

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: