From 7a718439762eddc57e38f089f49eeba66195de0e Mon Sep 17 00:00:00 2001 From: danielehc Date: Wed, 18 Sep 2024 19:25:34 +0200 Subject: [PATCH] Test CodeTabs --- .../content/docs/security/encryption/mtls.mdx | 16 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-) diff --git a/website/content/docs/security/encryption/mtls.mdx b/website/content/docs/security/encryption/mtls.mdx index f49eff7b2ebe..873248856b3c 100644 --- a/website/content/docs/security/encryption/mtls.mdx +++ b/website/content/docs/security/encryption/mtls.mdx @@ -257,7 +257,7 @@ Next, configure your client agents with the same method you used to [configure t The only file you need on the local disk to configure the Consul client agents using auto-encryption is the CA certificate `consul-agent-ca-.pem`. - + ```hcl addresses = { @@ -279,10 +279,6 @@ auto_encrypt = { } ``` - - - - ```json { "addresses": { @@ -305,7 +301,7 @@ auto_encrypt = { } ``` - + @@ -324,7 +320,7 @@ The client certificate is also signed by the same CA used for the server certifi Distribute the client certificates and the CA certificate `consul-agent-ca.pem` to every Consul client in the datacenter. Then add them to the client agent configuration. - + ```hcl addresses = { @@ -345,10 +341,6 @@ tls { } ``` - - - - ```json { "addresses": { @@ -370,7 +362,7 @@ tls { } ``` - +