Skip to content

xtr_security_jwt.command

The console commands: mint a key pair, mint a token, check the configuration.

CheckConfigCommand

Signs a probe token and reads it back, proving the keys work.

A deployment runs this after configuring its keys to learn — before a single request — that the signing key signs and the verifying key verifies. A failure names what went wrong.

GenerateKeyPairCommand

Mints a signing key and prints the private PEM and the public JWK set.

Nothing is written to disk unless --output-dir is given, so the keys can be piped into a secret store. With it, the private PEM and the public JWKS are written there, named by the key's identifier — never over a key file already in place unless --force says so, and never through a symbolic link planted where a key file is about to land.

GenerateTokenCommand

Loads a user by identifier and prints a token signed for it.

The user is loaded through one of the configured user providers: with several configured, --provider picks one by name; with exactly one, it is used without asking. The token manager signs the token, so it verifies against the same keys a firewall accepts.