The LDAP module lets BrynQ work with your on-premise Active Directory. BrynQ can:
Users are identified by a unique attribute, by default sAMAccountName.
Not for: Microsoft Entra ID (Azure AD) in the cloud, which BrynQ can reach directly.
During installation: select the LDAP module.
Afterwards: open the local admin dashboard > LDAP / Active Directory:
| Field | What to enter |
| Host | Your domain controller, for example ldap.company.com. |
| User | The service account BrynQ uses, as a distinguished name, for example CN=svc-brynq,OU=Service,DC=company,DC=com. |
| Password | The password of that service account. |
| Distinguished Name (Base DN) | Where BrynQ works in the directory, for example DC=company,DC=com. |
| Unique Identifier | The attribute that identifies a user. Default: sAMAccountName. |
| Options | Use SSL (LDAPS), if your domain controller requires it. |
Click Validate and Save. The Agent tests the connection before it saves the settings. The password is stored only on the server, protected with Windows data protection.
| What you see | What to do |
| Validate and Save fails | Check the host name, the service account (as a full distinguished name) and the password. Check that the Agent server can reach the domain controller. |
| Fails only with Use SSL | The domain controller must offer LDAPS with a certificate the Agent server trusts. |
| "Insufficient access rights" or a user is not created | The service account lacks rights on that OU or group. |
| A user cannot be found | Check the Base DN and the Unique Identifier. |
| A module 404 Not Found | The LDAP module is not enabled. Run the installer again and select LDAP. |