Create a Vault Transit provider with the given options.
Build a Vault API URL for the transit engine.
Common headers for Vault API requests.
List all keys, optionally filtered by usage or enabled state.
Optionalfilters: { usage?: string; enabled?: boolean }Retrieve metadata for a specific key by ID.
Create a new key with the given algorithm and usage.
Optionalmetadata: Record<string, string>Not supported: Vault Transit has no way to disable a key (the minimum encryption version cannot exceed the latest version). Restrict use of the key with a Vault policy instead.
Delete a key. Vault Transit has no deletion window: the key and every
version are destroyed at once, and data encrypted under it is lost.
Pass pendingWindowDays: 0 to confirm; any other value, including
none, is refused so a caller expecting a window cannot lose the key.
OptionalpendingWindowDays: numberEncrypt plaintext, binding the encryption context.
Optionalcontext: Record<string, string>Decrypt ciphertext; the encryption context must match.
Optionalcontext: Record<string, string>Sign data. algorithm is the Transit hash algorithm (default
"sha2-256"); RSA keys use Transit's default PSS padding, and Ed25519
ignores the hash.
Verify a signature. A wrong or malformed signature returns false; lookup, permission and transport errors are thrown.
Wrap an existing key with the managed key.
Optionalcontext: Record<string, string>Unwrap a wrapped key with the managed key.
Optionalcontext: Record<string, string>
HashiCorp Vault Transit secrets engine adapter.
Uses the Vault HTTP API to provide the unified KmsProvider interface. No additional SDK dependency is required — uses native
fetch.Example