Choose a supported operation
Algorithm names identify a cryptographic operation. They do not mean every key provider can generate every kind of key.
Managed generation uses the supported Google Cloud KMS algorithms. Requests for unsupported managed algorithms are rejected; the service must not relabel another algorithm to satisfy the request. Verification support does not provide a private signing key or enable a new issuance provider.
Keys and encoding
Useprovider: "KMS" to generate a dedicated managed issuer key. New issuer keys do not reuse the shared historical platform key. Existing records keep their original key identifiers; replacing a key does not rewrite their signatures.
Public-key registration takes base64url-encoded DER SubjectPublicKeyInfo. Registering a public key alone does not allow Truthlocks to mint with its private key. The mint endpoint does not ingest externally generated signatures.
Payloads and signatures use base64url without padding. ECDSA signatures in Truthlocks records use ASN.1 DER, not the fixed-width concatenation used in JWS. RSA-PSS uses a salt length equal to the digest length. New software RSA signing requires at least 3072 bits; verification retains support for registered RSA public keys of at least 2048 bits. The ECDSA curve must match the algorithm. See the algorithm definitions in RFC 7518.

