Documentation

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>

Usage

chronoctl token [flags]

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

Examples

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!


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.

Read more

InfluxDB v3 enhancements and InfluxDB Clustered is now generally available

New capabilities, including faster query performance and management tooling advance the InfluxDB v3 product line. InfluxDB Clustered is now generally available.

InfluxDB v3 performance and features

The InfluxDB v3 product line has seen significant enhancements in query performance and has made new management tooling available. These enhancements include an operational dashboard to monitor the health of your InfluxDB cluster, single sign-on (SSO) support in InfluxDB Cloud Dedicated, and new management APIs for tokens and databases.

Learn about the new v3 enhancements


InfluxDB Clustered general availability

InfluxDB Clustered is now generally available and gives you the power of InfluxDB v3 in your self-managed stack.

Talk to us about InfluxDB Clustered