To create an integration with an LDAP server:
The LDAP server settings window opens.
Do not change the default certificate validation mode unless you are using a root certificate to connect to the LDAP server.
The web address of the LDAP server is specified as follows: ldap://<host>:<port>
. For example: ldap://ldap.example.com:389
.
Bind DN is the distinguished name of the technical user account that is necessary for initial authentication and searching for a user in Active Directory.
You can specify the name of the technical user account in full or in the <login@domain>
format if your LDAP server supports this name format for authentication.
In the Bind DN password field, you must enter the password corresponding to the specified account name.
Before updating the solution, make sure that the Bind DN and Bind DN password fields are filled in. If these settings are not specified, LDAP server integration will not work.
For example, the base distinguished name for example.com is dc=example,dc=com
.
Kaspersky Container Security specifies attributes of parameter values, not the values themselves. For example, the solution specifies an attribute of the user name that can be used to find the user, not the user name directly.
The solution populates the integration creation form with the following attributes of parameter values:
Kaspersky Container Security uses the most general filter values to ensure operation for virtually all possible configurations. When configuring User filter and Group filter, we recommend that you store only those attribute values that are used in Active Directory.
If necessary, you can edit the values specified by the solution in the integration creation form.
Kaspersky Container Security will display a notification informing you of the successful connection to the LDAP server or a failure to establish the connection.
If the LDAP server certificate changes, reconfigure the integration.
You can use the configured integration when creating and assigning user roles.
Page top