Help The platform Import and SSO
Connect Active Directory or LDAP
On this page
Overview
This article covers the Connection section of an LDAP / Active Directory import and what is specific to LDAP; the other settings are common to all imports. This source does not offer SSO.
Network access: who queries the directory
| Your organization | What to plan for |
|---|---|
| Without the encryption option | Our servers connect from the internet: the server name must resolve only to public addresses (a private or reserved address is refused), and port 636 (LDAPS) or 389 (StartTLS) must be open to it. A directory reachable only from your internal network cannot be read this way. |
| With client-side encryption | Your Bexxo Protected agent reads the directory: its machine must reach the LDAP server. This is the only way to synchronize a directory that is not reachable from the internet. |
TLS is mandatory (ldaps or starttls): an unencrypted connection is refused. The certificate is checked against the name you enter: use the name that appears in the certificate, not an IP address.
Fill in the Connection section
Plan for a read-only service account that can read, under the base DNs, the people, groups and attributes listed below; an anonymous connection is refused. The optional fields left empty (user and group branches and filters, port, identifier attribute) take the default value: the base DN for the branches, and the directory type’s value for the rest. The fields to fill in carefully:
| Field | Content |
|---|---|
| Server (host) | Server name, without ldap://, for example ldap.exemple.ch. |
| Port and Encryption | ldaps (636 by default) or starttls (389 by default). |
| Connection DN (bind DN) | Full DN of the service account, for example CN=svc-bexxo,OU=Services,DC=exemple,DC=ch. |
| Base DN (base DN) | Starting point of the searches, for example DC=exemple,DC=ch. |
| Directory type | ad (Active Directory) or openldap: it sets the default values below. |
| Identifier attribute | A stable attribute that identifies a person or a group from one synchronization to the next. |
Directory type and default values
| Setting | ad | openldap |
|---|---|---|
| User filter | (&(objectClass=user)(objectCategory=person)) | (objectClass=inetOrgPerson) |
| Group filter | (objectClass=group) | (objectClass=groupOfNames) |
| Identifier attribute | objectGUID | entryUUID |
| Disabled account | Imported as inactive (attribute userAccountControl). | All people are imported as active. |
A custom LDAP filter replaces the default filter: include the object class in it, for example (&(objectClass=user)(objectCategory=person)(department=Vente)). It applies before the filters of the Filters section.
Do not change the identifier attribute after a first synchronization: the people already imported would no longer be recognized. An entry without this attribute is ignored and counted in a log warning.
Attributes read and groups
Only these attributes, plus the identifier attribute, are read: they are the only ones usable in the field matching and in the filters.
| Object | Attributes |
|---|---|
| Person | sn, givenName, cn, displayName, mail, mobile, telephoneNumber, preferredLanguage, dn, and accountEnabled (computed value: true or false) |
| Group | cn, displayName, description, member, dn |
Memberships are read from the member attribute of the groups. The server must support LDAP result pagination (“paged results”).
Beyond about 1500 members, Active Directory returns member only in batches and the synchronization fails rather than importing an incomplete group. Keep smaller groups or narrow the base DN of the groups.
Test and troubleshoot
The connection test authenticates, then searches for a person under the user base DN, with the user filter.
| Situation | What to check |
|---|---|
| Test failure, unencrypted organization | Does the name resolve to a public address, is the port open from the internet, does the certificate match the name entered? |
| Failure with a correct password | Does the encryption match the port (ldaps: 636, starttls: 389)? Is the connection DN complete? |
| The test succeeds, but no one is found | Do the base DN and the user filter match your accounts? Is the directory type the right one? |
| Entries ignored “for lack of a stable identifier” | The identifier attribute is not readable: clear the field to restore the default value, or give the service account the right to read it. |
| “Scope group(s) not found” | The group no longer exists under the group base DN or is no longer matched by their filter: remove it from Imported groups. |
| Encrypted organization: the agent does not respond within 10 minutes | Is the agent started, and does its machine reach the LDAP server? |
Didn’t find the answer? Contact us