aherman
/
boundary
mirror of https://github.com/hashicorp/boundary
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

backport of commit 4b3a2211c9

Browse Source
pull/4601/head
Danny Knights 2 years ago committed by GitHub
parent d89c773fd1
commit 2bf279cf05
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File

2
website/content/docs/integrations/vault/index.mdx
Unescape View File

@ -57,7 +57,7 @@ When you connect to a target that uses Vault for dynamic SSH certificates, a new
# Vault clients # Vault clients
## Boundary and Vault for secrets management ## Secrets management
Within Boundary, you can configure one or more credential stores. This could be a dedicated credential store per Boundary project, and/or multiple credential stores within the same Boundary project. You can either configure the credential store as static, which is Boundary's native store, or by integrating it with HashiCorp Vault. The purpose of the credential store that is integrated with Vault is to fetch secrets from Vault on behalf of Boundary users. Within Boundary, you can configure one or more credential stores. This could be a dedicated credential store per Boundary project, and/or multiple credential stores within the same Boundary project. You can either configure the credential store as static, which is Boundary's native store, or by integrating it with HashiCorp Vault. The purpose of the credential store that is integrated with Vault is to fetch secrets from Vault on behalf of Boundary users.

Write Preview
Loading…
Cancel
Save