LDAP Service Settings

LDAP monitor uses the following settings presented by LDAP Settings (ldapSettings) variable:

Property

Description

Enabled

Enables/disables LDAP monitoring.

Port

Port number the LDAP server can be connected on.

Username

User name used for authorization.

For Microsoft Active Directory, a User Principal Name (UPN) is typically accepted, e.g. user@domain.com.
For ALD PRO, a full Distinguished Name (DN) must be used instead, e.g. uid=svc_ldap,cn=users,cn=accounts,dc=example,dc=internal.

Password

Password used for authorization.

LDAP Query Context Name

Distinguished name of context to search in.

LDAP Query Filter

The filter expression to use for the search (according to RFC 2254). The value may be null or empty, in which case it is just ignored by the search.

ALD PRO Example

ALD PRO follows RFC 4513 strictly and requires a full Distinguished Name (DN) as the bind username.

The DN format defined by RFC 4513 consists of:

  • uid=<username> — the user's login name

  • one or more cn=<container> components — the organizational containers the user belongs to, from innermost to outermost

  • one dc=<part> component per dot-separated segment of the domain name

uid=<username>,cn=<container>,...,dc=<domain-part>,dc=<domain-part>

The LDAP plugin connects to the IP address of the Network Host device itself — no separate host field is required in the LDAP settings.

Property

Example Value

Enabled

Yes

Port

389

Username

uid=svc_ldap,cn=users,cn=accounts,dc=example,dc=internal

Password

Service account password

LDAP Query Context Name

cn=users,cn=accounts,dc=example,dc=internal

If the ALD PRO directory permits anonymous reads, Iotellect still requires a Username and Password in the LDAP settings. Create a dedicated service account in ALD PRO and enter its DN as Username along with the account's password.

Was this page helpful?