From e5c38f8a63ec6837eecda827b7bf114ec3d5aef3 Mon Sep 17 00:00:00 2001 From: RAMLAH MUNIR Date: Thu, 14 Aug 2025 21:16:18 +0500 Subject: [PATCH] =?UTF-8?q?Fix=20typo=20in=20caching=20docs:=20'Proving'?= =?UTF-8?q?=20=E2=86=92=20'Providing'?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Closes #41663 Signed-off-by: Ramlah7 --- docs/guides/server/caching.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/server/caching.adoc b/docs/guides/server/caching.adoc index 4c03e3c4d5e..b59e8c0726c 100644 --- a/docs/guides/server/caching.adoc +++ b/docs/guides/server/caching.adoc @@ -290,7 +290,7 @@ As an alternative, to disable the mTLS communication, and rely on the service me * Set the option `cache-embedded-mtls-enabled` to `false`. * Configure your service mesh to authorize only traffic from other {project_name} Pods for the data transmission port (default: 7800). -=== Proving your own keys and certificates +=== Providing your own keys and certificates Although not recommended for standard setups, if it is essential in a specific setup, you can configure the keystore with the certificate for the transport stack manually. `cache-embedded-mtls-key-store-file` sets the path to the keystore, and `cache-embedded-mtls-key-store-password` sets the password to decrypt it. The truststore contains the valid certificates to accept connection from, and it can be configured with `cache-embedded-mtls-trust-store-file` (path to the truststore), and `cache-embedded-mtls-trust-store-password` (password to decrypt it).