You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 19, 2023. It is now read-only.
Tokend has a pretty steep set of dependencies in Warden and Vault. Implementing a KMS provider would provide a single dependency and make for easier adoption.
This provider will implement the following endpoint: /v1/kms/decrypt. It will only accept POST requests and requires a body with a ciphertext key whose value is the encrypted secret from KMS.
The response from the endpoint will be:
{
"keyid": "<ARN OF KEY USED TO ENCRYPT>",
"plaintext": "<SECRET>"
}
Like the TransitProvider this is a non-renewable secret.
The text was updated successfully, but these errors were encountered:
Tokend has a pretty steep set of dependencies in Warden and Vault. Implementing a KMS provider would provide a single dependency and make for easier adoption.
This provider will implement the following endpoint:
/v1/kms/decrypt
. It will only accept POST requests and requires a body with aciphertext
key whose value is the encrypted secret from KMS.The response from the endpoint will be:
Like the
TransitProvider
this is a non-renewable secret.The text was updated successfully, but these errors were encountered: