From d0bef194f6219e7cfaf16464522ea571e01fd2a4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Fl=C3=A1vio=20Gomes=20da=20Silva=20Lisboa?=
 <flavio.lisboa@fgsl.eti.br>
Date: Wed, 19 Dec 2018 14:02:47 -0200
Subject: [PATCH] Documentation: behaviour with empty LDAP user-attributes
 undocumented #1010

---
 admin_manual/configuration_user/user_auth_ldap.rst | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/admin_manual/configuration_user/user_auth_ldap.rst b/admin_manual/configuration_user/user_auth_ldap.rst
index fb58fff56..d07046f30 100644
--- a/admin_manual/configuration_user/user_auth_ldap.rst
+++ b/admin_manual/configuration_user/user_auth_ldap.rst
@@ -735,3 +735,11 @@ is offline and will not try to connect again for the time specified in **Cache
 Time-To-Live**. If you have a backup server configured Nextcloud will connect to
 it instead. When you have scheduled downtime, check **Disable Main Server**  to
 avoid unnecessary connection attempts.
+
+Note
+----
+
+When a LDAP object's name or surname, that is display name attribute, by default 
+"displayname", is left empty, Nextcloud will treat it as an empty object, therefore
+no results from this user or AD-Object will be shown to avoid gathering of 
+technical accounts.