From 0e3ce03a3709e3704bb7daa14bb712965cf02438 Mon Sep 17 00:00:00 2001 From: Ali <59630460+ibrahimalihc@users.noreply.github.com> Date: Fri, 26 Jun 2020 09:18:04 -0400 Subject: [PATCH] docs: updated docs on Vault TLS settings (#7097) Co-authored-by: Ali Ibrahim --- website/pages/docs/configuration/vault.mdx | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/website/pages/docs/configuration/vault.mdx b/website/pages/docs/configuration/vault.mdx index 11ccd6832..5af2e31c4 100644 --- a/website/pages/docs/configuration/vault.mdx +++ b/website/pages/docs/configuration/vault.mdx @@ -59,14 +59,18 @@ vault { this will fallback to the default system CA bundle, which varies by OS and version. -- `cert_file` `(string: "")` - Specifies the path to the certificate used - for Vault communication. If this is set then you need to also set - `tls_key_file`. +- `cert_file` `(string: "")` - Specifies the path to the certificate used for + Vault communication. This must be set if + [tls_require_and_verify_client_cert](https://www.vaultproject.io/docs/configuration/listener/tcp/#inlinecode-tls_require_and_verify_client_cert) + is enabled in Vault. - `key_file` `(string: "")` - Specifies the path to the private key used for - Vault communication. If this is set then you need to also set `cert_file`. + Vault communication. If this is set then you need to also set + `cert_file`. This must be set if + [tls_require_and_verify_client_cert](https://www.vaultproject.io/docs/configuration/listener/tcp/#inlinecode-tls_require_and_verify_client_cert) + is enabled in Vault. -- `namespace` `(string: "")` - Specifies the [Vault namespace](https://www.vaultproject.io/docs/enterprise/namespaces) +- `namespace` `(string: "")` - Specifies the [Vault namespace](https://www.vaultproject.io/docs/enterprise/namespaces/index.html) used by the Vault integration. If non-empty, this namespace will be used on all Vault API calls.