LDAP connections are created and managed under Settings → LDAP server connections in the KUMA web interface. The LDAP server connections table shows the tenants for which LDAP connections were created. When a tenant is selected, the connections with LDAP servers created for it are displayed.
To add a tenant to the LDAP server connections section:
In the KUMA web interface, under Settings → LDAP server connections, click Add.
In the LDAP connections window, in the Tenant drop-down list, select the relevant tenant and click Save.
The tenant will be added and displayed in the LDAP server connections table.
If you select a tenant, the LDAP connections window opens to show a table containing existing LDAP connections. Connections can be created or selected for editing.
After integration is enabled, information about Active Directory accounts becomes available in the alert window, the correlation events detailed view window, and the incidents window. If you click an account name in the Related users section of the window, the Account details window opens with the data imported from Active Directory.
The following account attributes can be requested from Active Directory:
AccountExpires
BadPasswordTime
cn
co
company
department
description
displayName (this attribute can be used for search during correlation)
distinguishedName (this attribute can be used for search during correlation)
division
EmployeeID
givenName
l
lastLogon
lastLogonTimestamp
mail (this attribute can be used for search during correlation)
MailNickname
ManagedObjects
manager
memberOf (this attribute can be used for search during correlation)
mobile
name
objectCategory
objectGUID (this attribute always requested from Active Directory even if a user doesn't specify it)
ObjectSID
PhysicalDeliveryOfficeName
pwdLastSet
sAMAccountName (this attribute can be used for search during correlation)
SAMAccountType
sn (this attribute can be used for search during correlation)
StreetAddress
TelephoneNumber
title
userAccountControl (this attribute can be used for search during correlation)
userPrincipalName (this attribute can be used for search during correlation)
WhenChanged
whenCreated
In the Data storage time field, you can specify how many days KUMA will store information received from LDAP after such information stops being received from the Active Directory server.