From e5657c994d6c16048eff6e00585dcd31d3612fe9 Mon Sep 17 00:00:00 2001 From: "Chris S. Kim" Date: Wed, 4 Oct 2023 16:19:57 -0400 Subject: [PATCH] Backport change --- website/content/docs/upgrading/upgrade-specific.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/website/content/docs/upgrading/upgrade-specific.mdx b/website/content/docs/upgrading/upgrade-specific.mdx index 7fce96adcd3..c4f969fc7c1 100644 --- a/website/content/docs/upgrading/upgrade-specific.mdx +++ b/website/content/docs/upgrading/upgrade-specific.mdx @@ -36,6 +36,14 @@ to use TLS for contacting the HTTP API, it will also incorrectly enable TLS for Users should not upgrade to 1.14.0 if they are using plaintext gRPC connections in conjunction with TLS-encrypted HTTP APIs. +#### Vault Enterprise as CA ((#vault-enterprise-as-ca-1-14)) +Using Vault as CA with Consul version 1.14.10 will fail to initialize the CA if [`namespace`](/consul/docs/connect/ca/vault#namespace) is set +but [`intermediate_pki_namespace`](/consul/docs/connect/ca/vault#intermediatepkinamespace) or [`root_pki_namespace`](/consul/docs/connect/ca/vault#rootpkinamespace) +are empty. This is a bug which will be fixed in a future version. + +To work around this issue, users must explicitly set [`intermediate_pki_namespace`](/consul/docs/connect/ca/vault#intermediatepkinamespace) and +[`root_pki_namespace`](/consul/docs/connect/ca/vault#rootpkinamespace) to the same value as [`namespace`](/consul/docs/connect/ca/vault#namespace). +Set your configuration by calling [set-config](/consul/commands/connect/ca#set-config) then use [get-config](/consul/commands/connect/ca#get-config) to check. #### Changes to gRPC TLS configuration