This article provides detailed steps to map users from a specific Organizational Unit in Kerio Connect, which may be useful in cases when you want to differentiate between additional Active Directory and LDAP (Lightweight Directory Access Protocol) containers.
The LDAP database can use containers to differentiate between objects. An Organizational Unit is the full name of the LDAP object. To use Organizational Units with the Kerio Connect domain mapping, you need its Distinguished Name (DN).
Kerio Connect maps users from the default LDAP location, which is defined by the DN in this format:
There are two (at least) domains on Kerio Connect server mapping users from the same directory service. Both email domains on the Kerio Connect server contain the same users. There is a need to differentiate between users according to the email domain to which the user belongs.
By default, the Kerio Connect maps all users from all containers in the Active Directory, as this is the top-level structure of the Active Directory tree.
Warning: The instructions below include changing the configuration file. If the instructions are not followed correctly, they may cause problems with the functioning of the product. Only proceed if you are comfortable doing so. It is also good practice to take a backup before making any changes.
Configure Active Directory mapping. For additional information, refer to Connecting Kerio Control to Active Directory Service.
Stop the Kerio Connect service.
Open the mailserver.cfg configuration file, which is located in the installation directory.
<list name="Ldap">value in the configuration file.
In this section of the configuration file, locate your domain definition as highlighted in the below example:
GroupBasedDNsearch locations according to your path. In this example, the location was changed to the Support department:
Save the configuration file.
Start the Kerio Connect service.
Kerio Connect now differentiates between additional Active Directory and LDAP containers.