GITBOOK-385: change request with no subject merged in GitBook

Author: defguard-community

enterprise/all-enteprise-features/ldap-and-active-directory-integration/settings-table.md

@@ -37,6 +37,11 @@ Changing the RDN attribute may cause your users to be re-added to Defguard, caus
 * `Username attribute`: The username attribute which will be used to set the username of a Defguard user. The following restrictions apply:
   * Only alphanumeric characters except for  <kbd>.</kbd>, <kbd>-</kbd> or <kbd>\_</kbd>
   * At least 1 and at most 64 characters
+
+{% hint style="danger" %}
+To use this feature, your LDAP user entries must posses the "memberOf" attribute (or it's equivalent, defined using the member attribute), which may not be available by default on your LDAP server. This may require enabling an appropriate module.&#x20;
+{% endhint %}
+
 * `Limit synchronization to these groups`: limits the synchronization scope to only the members of the selected groups, this works both ways:
   * Changes in Defguard will be propagated to LDAP only if a user belongs to a given group in Defguard.
   * If the two way synchronization is enabled, only the users belonging to the specified groups will be fetched from the LDAP server.

enterprise/all-enteprise-features/ldap-and-active-directory-integration/two-way-ldap-and-active-directory-synchronization.md

@@ -4,12 +4,10 @@ icon: arrow-right-arrow-left
 
 # Two-way LDAP and Active Directory synchronization
 
-{% hint style="warning" %}
-This is an alpha feature available in Defguard core v1.3.0 alpha builds and above. It may not be production ready yet and may have some bugs. Report any issues you find on our [GitHub](https://github.com/DefGuard/defguard/issues).
-{% endhint %}
-
 {% hint style="danger" %}
-Make sure to be aware of the mechanisms described in [#authority-and-full-synchronization](two-way-ldap-and-active-directory-synchronization.md#authority-and-full-synchronization "mention")and [#first-synchronization](two-way-ldap-and-active-directory-synchronization.md#first-synchronization "mention") before enabling this feature, as improper use may cause loss of user data.
+Make sure to be aware of the mechanisms described in [#authority-and-full-synchronization](two-way-ldap-and-active-directory-synchronization.md#authority-and-full-synchronization "mention") and [#first-synchronization](two-way-ldap-and-active-directory-synchronization.md#first-synchronization "mention") before enabling this feature.\
+\
+We recommend testing the integration first in a non-production environment, as improper configuration may cause loss of user data.
 {% endhint %}
 
 The LDAP synchronization allows for synchronizing users and groups between Defguard and your LDAP server.