From f23ebd8eb70ecb512eb21b3eba2cb2176a3894f9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Max=20Neunh=C3=B6ffer?= Date: Mon, 5 Mar 2018 13:42:31 +0100 Subject: [PATCH] Improve the description of --ldap.tls-version (#4747) --- .../Books/Manual/Administration/Configuration/Ldap.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Documentation/Books/Manual/Administration/Configuration/Ldap.md b/Documentation/Books/Manual/Administration/Configuration/Ldap.md index 47a0e86414..46efaa23b6 100644 --- a/Documentation/Books/Manual/Administration/Configuration/Ldap.md +++ b/Documentation/Books/Manual/Administration/Configuration/Ldap.md @@ -153,8 +153,10 @@ the following options are available. Note: *TLS is not supported under Windows*: protocol via the LDAP url (see previous section), then ArangoDB will use the `STARTTLS` protocol to initiate TLS. This is the recommended approach. - - `--ldap.tls-version` the tls version that should be used. - Available versions are `1.0`, `1.1` and `1.2`. The default is `1.2`. + - `--ldap.tls-version` the minimal TLS version that ArangoDB should accept. + Available versions are `1.0`, `1.1` and `1.2`. The default is `1.2`. If + your LDAP server does not support Version 1.2, you have to change + this setting. - `--ldap.tls-cert-check-strategy` strategy to validate the ldap server certificate. Available strategies are `never`, `hard`, `demand`, `allow` and `try`. The default is `hard`.