ghcr.io/spruceid/didkit-cli
.Note: You can pass JWKs either by sharing a volume with:docker run --volume
or by passing the JWK directly with:docker run -e JWK=$MY_JWK
ordocker run didkit-http --jwk $MY_JWK
.
didkit help
, didkit generate-ed25519-key
, etc.help
didkit
and its subcommands.generate-ed25519-key
key-to-did
key-to-verification-method
-k, --key-path <file>
(required, conflicts with jwk): Filename of JWK file-j, --jwk <jwk>
(required, conflicts with key-path): JWK.vc-issue-credential
RS256
is used for it, for RsaSignature2018.--key-path
correspond to linked data proof options as specified in ld-proofs and vc-http-api.-c, --created <created>
- created property of the proof. ISO8601 datetime. Defaults to the current time.-k, --key-path <key>
(required, conflicts with jwk): Filename of JWK for signing.-j, --jwk <jwk>
(required, conflicts with key-path): JWK for signing.-v, --verification-method <verification-method>
verificationMethod property of the proof. URI for proof verification information, e.g. a public key identifier.RSA
OKP
(curve
: Ed25519
)vc-verify-credential
-c, --created <created>
- The created property of the proof must be on or after the given ISO8601 datetime. Defaults to the current time.-v, --verification-method <verification-method>
- The verificationMethod property of the proof must equal this value.{"checks": [],"warnings": [],"errors": []}
checks
- Array of strings indicating checks completed on the credential.warnings
- Array of warnings encountered during validation or verification.errors
- Array of strings indicating errors encountered during validation or verification. If errors
is empty, the credential is verified.vc-issue-presentation
vc-verify-presentation
HTTP_PROXY
to have DIDKit use a proxy. Both HTTP and SOCKS protocols are supported. See the "proxies" section of the DIDKit docs for more details.