From ec0f8c11a918b9faef82f44a0cfe7e3d0b8b1918 Mon Sep 17 00:00:00 2001 From: lcawley Date: Tue, 1 May 2018 15:27:29 -0700 Subject: [PATCH] [DOCS] Addresses feedback --- .../authentication/configuring-ldap-realm.asciidoc | 8 ++++---- .../en/security/securing-communications/tls-ldap.asciidoc | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/x-pack/docs/en/security/authentication/configuring-ldap-realm.asciidoc b/x-pack/docs/en/security/authentication/configuring-ldap-realm.asciidoc index 9d124a66a0753..b43a0911e0467 100644 --- a/x-pack/docs/en/security/authentication/configuring-ldap-realm.asciidoc +++ b/x-pack/docs/en/security/authentication/configuring-ldap-realm.asciidoc @@ -14,10 +14,10 @@ operation, a user search mode and a mode with specific templates for user DNs. + -- LDAP user search is the most common mode of operation. In this mode, a specific -user with permission to search the LDAP directory is used to search for the -authenticating user DN based on its username and an LDAP attribute. Once found, -the user is authenticated by attempting to bind to the LDAP server using the -found DN and the provided password. +user with permission to search the LDAP directory is used to search for the DN +of the authenticating user based on the provided username and an LDAP attribute. +Once found, the user is authenticated by attempting to bind to the LDAP server +using the found DN and the provided password. If your LDAP environment uses a few specific standard naming conditions for users, you can use user DN templates to configure the realm. The advantage of diff --git a/x-pack/docs/en/security/securing-communications/tls-ldap.asciidoc b/x-pack/docs/en/security/securing-communications/tls-ldap.asciidoc index 00b280a5466f9..f10ced77f718a 100644 --- a/x-pack/docs/en/security/securing-communications/tls-ldap.asciidoc +++ b/x-pack/docs/en/security/securing-communications/tls-ldap.asciidoc @@ -32,7 +32,7 @@ xpack: certificate_authorities: [ "CONFIG_DIR/x-pack/cacert.pem" ] -------------------------------------------------- -The CA cert must be a PEM encoded certificate. +The CA certificate must be a PEM encoded. NOTE: You can also specify the individual server certificates rather than the CA certificate, but this is only recommended if you have a single LDAP server or