Update doc (#2589)

doc/sources/admin/finduser.rst

@@ -22,6 +22,13 @@ Just enable it in the Manager (section “plugins”). Then, set searching attri
    -  **Searching attributes**: For each attribute, you have to set a key (attribute as defined in UserBD) and a value that will be display in login form (placeholder). A value can be a multivalued list separated by multiValuesSeparator parameter (General Parameters > Advanced parameters > Separator). See note below.
    -  **Excluding attributes**: You can defined here attributes used for excluding accounts. Set keys corresponding to UserBD attributes and values to exclude. A value can be a multivalued list separated by multiValuesSeparator parameter (General Parameters > Advanced parameters > Separator)
 
+.. note::
+
+   By default, simple searching attributes are mandatory to restrict the number of entries to return. To set an attribute as optional,
+   you can use the following syntax ::
+
+         uid##1  =>  UID
+
 .. note::
 
    You can provide a 'multiValuesSeparator' separated list of allowed searching values that will be displayed as an HTML <select> list ::
@@ -36,10 +43,6 @@ Just enable it in the Manager (section “plugins”). Then, set searching attri
 
    Entries are sorted by alphabetical order.
 
-.. attention::
-
-    LDAP filter works only if an objectClass is set.
-
 .. attention::
 
     Searching request is built based on provided parameters value depending on users backend like this:
@@ -52,9 +55,4 @@ Just enable it in the Manager (section “plugins”). Then, set searching attri
 
 .. danger::
 
-    With AuthChoice, you must set which module will be called by this plugin (:doc:`Backend choice by users<authchoice>`).
-
-
-
-.. |image0| image:: /documentation/beta.png
-   :width: 100px
+    With AuthChoice, you must set which module will be called by this plugin (:doc:`Backend choice by users<authchoice>`).