Skip to content

Commit d53a1d8

Browse files
defguard-communitygitbook-bot
authored andcommitted
GITBOOK-406: change request with no subject merged in GitBook
1 parent ba58691 commit d53a1d8

1 file changed

Lines changed: 23 additions & 0 deletions

File tree

  • enterprise/all-enteprise-features/ldap-and-active-directory-integration

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

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,8 @@ description: How to configure connection between Defguard instance and LDAP.
88
Active Directory support is available in Defguard ≥ v1.3.0
99
{% endhint %}
1010

11+
12+
1113
## Setup
1214

1315
First, navigate to the settings page and select the LDAP tab.
@@ -55,3 +57,24 @@ The "cn" attribute has been configured as the user's RDN as that's what used in
5557
<figure><img src="../../../.gitbook/assets/image (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
5658

5759
This is an example configuration for an OpenLDAP server integrated with Samba (hence `sambaSamAccount` object class). The `inetOrgPerson` has been set as the user structural class which adds attributes to the LDAP user like `email` or `mobile`. `simpleSecurityObject` class has been added for the ability to set passwords in LDAP.
60+
61+
62+
63+
## Known issues
64+
65+
### Multiple nested OUs
66+
67+
Using the integration with multiple nested organizational units may currently lead to some unexpected behavior. The following issues are known to occur:
68+
69+
* If you have duplicate user RDNs across multiple OUs a database error may occur: `Duplicate key violates unique constraint 'unique_ldap_rdn'` , causing issues with two way synchronization. This would happen in the following scenario:
70+
* `CN=user1,OU=ou1,OU=ou,DC=example`
71+
* `CN=user1,OU=ou2,OU=ou,DC=example`
72+
* Limiting synchronization to selected groups may not work if your user's DN doesn't match the user search base:
73+
74+
* Search base: `OU=ou,DC=example`
75+
* User's DN: `CN=user1,OU=ou1,OU=ou,DC=example`&#x20;
76+
77+
In this example, the user's DN has deeper nesting than the search base, preventing matching them during the group members lookup.
78+
79+
To fix this problem, you should limit the search base to one organizational unit only, if possible. Otherwise we are working on a solution, the status can be tracked in the following issue: [https://github.com/DefGuard/defguard/issues/1242](https://github.com/DefGuard/defguard/issues/1242).
80+

0 commit comments

Comments
 (0)