From 4f1cd3077f6bada23a6f9bac58816454a83423d7 Mon Sep 17 00:00:00 2001 From: Dustin Frank Date: Wed, 10 Nov 2021 08:57:46 +0100 Subject: [PATCH] Fix (#1042) Co-authored-by: stianst --- server_installation/topics/network/outgoing.adoc | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/server_installation/topics/network/outgoing.adoc b/server_installation/topics/network/outgoing.adoc index 2986f2ab64..761fdcfec9 100644 --- a/server_installation/topics/network/outgoing.adoc +++ b/server_installation/topics/network/outgoing.adoc @@ -169,7 +169,6 @@ You can add your truststore configuration by using the following template: - @@ -184,11 +183,11 @@ file:: This is what the trustore does. The keystore contains one or more trusted host certificates or certificate authorities. This truststore file should only contain public certificates of your secured hosts. - This is _REQUIRED_ if `enabled` is true. + This is _REQUIRED_ if any of these properties are defined. password:: - Password for the truststore. - This is _REQUIRED_ if `enabled` is true. + Password of the keystore. + This is _REQUIRED_ if any of these properties are defined. hostname-verification-policy:: `WILDCARD` by default. @@ -196,7 +195,3 @@ hostname-verification-policy:: `ANY` means that the hostname is not verified. `WILDCARD` Allows wildcards in subdomain names i.e. *.foo.com. `STRICT` CN must match hostname exactly. -enabled:: - If false (default value), truststore configuration will be ignored, and certificate checking will fall back to JSSE configuration as described. - If set to true, you must configure `file`, and `password` for the truststore. -