Adding transit logical backend #12
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
❤️ Do you think we should add docs/usage for this to the website? I think this is a really strong use-case for Vault that people will just "get", you know? |
|
@sethvargo Of course we will :) The docs are still mostly not done. |
jeffwecan
added a commit
to jeffwecan/vault
that referenced
this pull request
Nov 7, 2018
[SRE-1267] Peer Zabbix VPC to Vault for monitoring, etc.
briankassouf
pushed a commit
that referenced
this pull request
Aug 24, 2020
Bring over PSIRT-37 changes from ENT to 1.4.x
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds the "transit" logical (secret) backend. It is used for encryption and decryption of values in transit, and does not actually store the values. It is used by creating a named policy, such as "oauth" by writing to "policy/oauth". This creates a named encryption key (currently defaults to 256bit AES-GCM).
Clients can then use the "encrypt/oauth" and "decrypt/oauth" endpoints to encrypt and decrypt data respectively.
The use case for this is to allow Vault to manage the encryption keys, but allow clients to perform cryptographic operations. For example, web servers can encrypt oauth tokens and store the cipher text in a database. When the token is needed, it flows through Vault to be decrypted and then used. This means the web servers never have access to the encryption key, the plaintext oauth token is only available in transit (hence the name), but is stored encrypted at rest.