eBrigade LDAP / Active Directory module
Connect eBrigade to your corporate directory
Connect eBrigade to your Active Directory or OpenLDAP directory: delegated authentication, configurable mapping of attributes to eBrigade fields and two-way user synchronisation. Import your accounts from the directory and push eBrigade creations or updates to LDAP, manually or by cron.
These buttons are about this optional module: add-on pricing and a 1-month trial of the module.
Two-way synchronisation and authentication with your Active Directory or OpenLDAP directory.
What is the eBrigade LDAP / Active Directory module?
Two-way synchronisation and authentication with your Active Directory or OpenLDAP directory. It is available as an option so that each organisation can enable it as needed.
Why use the LDAP / Active Directory module?
In organisations with an Active Directory or OpenLDAP directory, creating and maintaining eBrigade accounts separately leads to duplicates, forgotten passwords and re-keying. Your IT teams waste time synchronising two identity repositories by hand, without knowing the real state of the accounts on either side.
What the LDAP / Active Directory module changes in eBrigade
The module connects eBrigade to your directory in both directions. Users sign in with their corporate credentials (bind by uid), you import LDAP accounts into eBrigade and push eBrigade creations or updates to the directory, anchored on the uid. The configuration (host, port, DN, encryption) can be tested in one click from the settings, and every synchronisation is logged in a viewable history.
What you can do with LDAP / Active Directory
The module synchronises in both directions: import of LDAP users into eBrigade and push of eBrigade creations or updates to the directory, anchored on the uid.
Import LDAP users one by one, by range, or the entire directory, depending on the scope you want to synchronise.
Map LDAP attributes to eBrigade fields (surname, first name, status, email, organisation, address…) from the interface, with some fields marked as required.
Plain (ldap://), encrypted (ldaps://) or StartTLS connection, with a one-click connection test from the settings before enabling the module.
Users authenticate by bind with their corporate credentials, with no separate eBrigade password to manage. Optionally blocking the local password forces use of the directory.
Automatic synchronisation by CLI cron or token-secured HTTP, with an operations history and synchronisation monitoring from the interface. Compatible with Active Directory and OpenLDAP.
Step by step
Enter the host, port, service account, OU and base DN, then choose the encryption mode (plain, LDAPS or StartTLS) from the eBrigade settings. A test button validates the connection before anything is enabled.
Map LDAP attributes to eBrigade fields (surname, first name, status, email, organisation…), some of which are required. Bind authentication works as soon as you connect, even before the mapping is fully configured.
Import LDAP users into eBrigade — one by one, by range or all — and push eBrigade creations or updates to the directory, anchored on the uid. Every operation is recorded in the history.
Schedule synchronisation via CLI cron or a token-secured HTTP call, and follow the status of operations from the module’s built-in monitoring.
Where this module really pays off
Fire and rescue services (SDIS) & local authorities: import staff from the authority’s Active Directory, with no manual entry of accounts in eBrigade.
Multi-site organisations: synchronise users between the central LDAP directory and eBrigade, in both directions, manually or by cron.
Healthcare facilities & SAMU (French emergency medical service): unified authentication with the existing directory and LDAPS or StartTLS transport encryption.
Organisations with an OpenLDAP directory: push accounts created in eBrigade to the directory, anchored on the uid, to keep a single source of truth.
Demanding IT teams: block the local password to force authentication through the corporate directory.
Frequently asked questions
Which directories are supported?
Microsoft Active Directory and OpenLDAP. Configuration (host, port, service account, OU, base DN, encryption) is done from the dedicated settings page in eBrigade, with a one-click connection test.
Does synchronisation only run from the directory to eBrigade?
No. The module is two-way: you import LDAP users into eBrigade (one by one, by range or all) and also push eBrigade creations or updates to the directory. Matching is anchored on the uid.
Do we need to configure the mapping before users can sign in?
No. Bind authentication with the uid works as soon as the connection is configured and tested. Mapping attributes to eBrigade fields is used for data synchronisation and can be defined afterwards.
Is the transport encrypted?
Yes, as you choose: plain ldap://, ldaps:// or StartTLS. LDAPS or StartTLS are recommended in production. The mode is selected in the module configuration.
Can we force authentication through the directory?
Yes. An option lets you block local password sign-in to force LDAP authentication. Synchronisations can be automated via a CLI cron or a token-secured HTTP call, and every operation is logged in the history.
Is the LDAP module compatible with SSO and MFA?
Yes. LDAP handles authentication and synchronisation via the directory, Single sign-on (SSO) delegates authentication to an identity provider and Two-factor authentication (MFA) adds a second factor. All three can work together according to your security policy.