Skip to content
Registry StackDocsDevelopment (unreleased)

evidencectl keygen client-assertion command reference

View as Markdown

Keypair a source’s clientAssertionKeyRef points at, for a token endpoint that authenticates the client by signed assertion.

This page is generated from the public Clap command tree for Registry Stack source version 0.46.1 and catalog SHA-256 61bebbb88fe15e4da92e2b0adbca0cd5b1a47b8eac38f4b91a15095011368a43. Hidden implementation commands are omitted.

evidencectl keygen client-assertion [OPTIONS] --output-dir <OUTPUT_DIR>
OptionAlways requiredDefaultValuesEnvironmentDescription
--output-dir <OUTPUT_DIR>Yesn/an/an/aSecret directory receiving the private JWK file (created 0700)
--public-output <PUBLIC_OUTPUT>Non/an/an/aPublic JWK output path; defaults to a file inside the secret directory
--private-name <PRIVATE_NAME>Non/an/an/aName of the private JWK file, which is the secret:file/NAME a source’s clientAssertionKeyRef points at; defaults to one naming the algorithm. The public half follows it as NAME-public.jwk.json
--algorithm <ALGORITHM>Noes384es384, rs384n/aSignature algorithm the assertion is signed with
--format <FORMAT>Nohumanhuman, json, junitn/aEmit the selected command’s report in this format. junit is accepted only by test and fixtures run
-h, --helpNon/an/an/aPrint help (see a summary with ‘-h’)

After changing a public command, argument, option, default, environment binding, or help description, run cargo run --locked -p registry-cli-docs -- --write, commit crates/registry-cli-docs/catalog.json, then run npm run generate from docs/site.