Generate Signing Keyset
generate-signing-keyset creates and rotates local P-256 signing keysets and
derives RFC 7638 SHA-256 public JWK thumbprints from private keysets. It is the
fallback for deployments that do not source signing keys from Vault or OpenBao.
Generate a keyset
The command writes a combined document that can be split into the two files consumed by NVIDIA Workload Identity Keys:
Create the two files consumed by NVIDIA Workload Identity Keys:
Add a key
add reads a combined keyset from standard input, retains its current keys,
appends a new P-256 key, and leaves the current key active:
The input must contain at least one valid ES256 private key and its current
active kid. The output uses the same combined document format as generate.
Use thumbprints to identify the added key before changing active_kid after
the new public key has propagated.
Generate thumbprints
thumbprints reads a private keyset from standard input and writes the ordered
RFC 7638 identifiers derived from its public keys:
The input may be either a combined generator document or a keyset.json
document containing the keys array. SEC 1 EC, PKCS#1 RSA, and PKCS#8 private
keys are supported.
NVIDIA Workload Identity Keys files
keyset.json:
active-kid.json:
The local E2E uses this generator because it does not deploy a Vault or OpenBao signing-key source.
The tool has no runtime dependencies beyond a secure operating-system random
source. generate and add output private key material. thumbprints outputs
only derived identifiers.