Active Directory / LDAP
Mirror users, groups and computers from Active Directory over LDAP, or from Entra ID, and optionally provision Aegis accounts from them.
Active Directory (Microsoft's directory of users, groups and machines) is where most organisations already record who works there and which computers they use. This connector reads that directory into Aegis as a read-only directory mirror (a copy Aegis keeps per connection). The mirror is used when you import machines into the CMDB and when a data-subject request searches for a person. On top of the mirror sits an optional user provisioning bridge, which can turn directory users into Aegis accounts. Provisioning is switched off when a connection is created and does nothing until you opt in.
At a glance
| Direction | Into Aegis. The connector reads the directory; it never writes to it. |
|---|---|
| What it brings in | User, group and computer objects of the directory, with group membership. |
| Where it lands | A directory mirror per connection, and, when user provisioning is switched on, Aegis users: invitations for joiners, roles from group mappings, and deactivation of leavers linked to that connection. There is no screen that lists the mirrored objects; you see them where they are used, such as the CMDB import. |
| Credentials and permissions | For LDAP: the server address and a bind account that can read the directory. For Entra ID: either the Microsoft integration your organisation has already signed in with, or an app registration with read access to users and groups. |
| Owner of imported records | Mirrored objects have no owner. Provisioned users are invited, so they confirm their email and set up their own sign-in. |
| When it runs |
Connections are checked every five minutes against their own sync
schedule, and on demand with the Sync now button. A new
connection syncs every six hours; the screen does not offer a way to
change that schedule.
|
| Set it up |
/connectors/ad, by people allowed to configure
connectors, on a plan that includes the connector. Several
connections can live under this one tile.
|
Who uses it
-
Manager opens the list and
every connection, creates connections, edits them, runs
Sync nowandTest connection, and changes the provisioning policy, group mappings and user ledger. -
Admin can do all of that and is
the only role that sees
Delete connection. - Contributor and Viewer cannot open these pages: Aegis redirects them to the access-denied page.
The pages also sit behind the same module and licence feature as the
Azure connector. When either is off for your
organisation, /connectors/ad shows a not-found page instead of the
list.
What's on this screen
Open Connectors and select the
Active Directory / LDAP tile. The page at
/connectors/ad has:
-
A breadcrumb (
Connectors / Active Directory / LDAP) and the titleActive Directory / LDAP Connections, with a line explaining that you select a connection for sync, provisioning and group-to-role mappings. -
The
Connectionsheading with theNew connectionbutton on the right, shown only to people who may change connectors. -
The connections table, with the columns
Name(a link to the connection),Type(LDAPorMicrosoft Entra ID) andLast sync(a status badge such asCompletedorFailed, orNever synced). - An empty state when there are no connections yet: “No AD/LDAP connections yet. Create one to start mirroring your directory.”
No screenshot of this screen was captured for this edition of the guide.
Create a connection
-
Select
New connection. A dialog titledNew AD/LDAP connectionopens withNameandType, set toLDAP. -
Enter a
Name.Create connectionstays unavailable until the name has text in it. -
For an LDAP directory, fill in
LDAP URL,Base DN(where in the directory to start reading),Bind DN(the read account) andBind password. All four are required. The hint under the URL explains the rules:ldaps://uses TLS directly,ldap://is upgraded with StartTLS before the password is sent, and unencrypted binds are not supported. -
For Entra ID, set
TypetoMicrosoft Entra ID. The boxUse the signed-in Microsoft integration (no client secret needed)is ticked. Clear it to enter aClient ID,Client secretandTenant IDinstead. -
Select
Create connection. Aegis opens the new connection's detail page. If the save fails, a red message under the form gives the reason, or, when there is none, asks you to check the fields and try again.
When an Entra ID connector is
configured, choosing Microsoft Entra ID shows a notice. For the
tenant it is connected to, the Entra ID connector takes over directory reads
and data-subject lookups. Add an Entra ID connection here only for user
provisioning or for another tenant. The notice links to
Open the Entra ID connector.
The connection page: Overview
Select a connection's name to open /connectors/ad/<id>. Under
the breadcrumb and the title Active Directory / LDAP connection are
two tabs, Overview and Provisioning. The chosen tab is
kept in the address, so a link or a reload returns to it.
Overview shows a card with Name, Type,
Last sync status, Last synced (or Never),
Enabled and, for LDAP, the LDAP URL. Above the card is
a row of buttons.
-
Select
Edit. The card turns into a form in the page (not a dialog) withNameand, for LDAP,LDAP URL,Base DN,Bind DN,Bind passwordandSearch filter (optional). Below them are the boxesEnabled,Sync users,Sync groupsandSync computers. -
Leave
Bind passwordblank to keep the stored password; it is never shown. SelectSave changes. A “Connection updated” message appears and the card returns.Canceldiscards the edit. -
Select
Test connection. Aegis tries to reach and bind to the directory, then shows “Connection test succeeded” or “Connection test failed”. The failure message is deliberately generic and does not repeat the directory's own error text. -
Select
Sync nowto refresh the mirror straight away. The button readsSyncing...while it runs, then “Sync completed”, “Sync failed”, or “Sync finished with errors” when some objects were not synced. The button is unavailable on a disabled connection; pointing at it shows the tooltip “Enable the connection to sync”. -
An Admin can select
Delete connection. A confirmation dialog warns that the connection and its synced directory objects are removed permanently. Confirm, and Aegis returns you to the list.
The connection page: Provisioning
The Provisioning tab bridges the mirror into Aegis user accounts.
Its subtitle states the rule: the defaults are sync-only and fail-closed, and
nothing is created, changed or deactivated until you opt in. The tab has four
sections, top to bottom. People without the right to change connectors see a
read-only notice and greyed-out fields.
Provisioning policy
| Setting | Choices | Default |
|---|---|---|
Enable user provisioning |
On or off. When off, the mirror keeps running but no Aegis users change. | Off |
Provisioning mode |
Sync only (record state, take no action),
Flag for review (queue new users for a person) or
Auto-provision (send invitations automatically)
|
Sync only |
Leaver policy |
Ignore, Flag for review or
Auto-deactivate
(ban the account and revoke its sessions)
|
Flag for review |
Conflict policy |
Skip (never touch a user from another source) or
Adopt
(link and take over the existing user)
|
Skip |
Enable group → role mapping and
Default role
|
When mapping is off, everyone provisioned gets the default role. When on, the group mappings decide. | Off; Viewer |
Directory attribute mapping |
Which directory attributes hold the email, the name and (for LDAP) the logon name | Blank |
Mass-action guard ratio |
A fraction between 0 and 1 (0.5 means 50%) | 0.5 |
Choosing Auto-provision, Auto-deactivate or
Adopt shows a red warning beside the field that explains what will
happen to real accounts. Select Save settings to store the policy.
Group → role mappings
-
Select
Add mapping. A form opens withGroup (DN or GUID),Aegis role,PriorityandActive. -
Enter the directory group, choose a role, and set the priority: when a user
is in several mapped groups, the higher priority wins. Select
Save. The mapping appears in the table with the columnsGroup,Role,Priority,ActiveandActions. -
Use
EditorDeleteon a row. Deleting asks for confirmation; members fall back to the default role on the next run.
A mapping to Admin gives every member of that directory group full control of Aegis. The section shows this warning permanently. Keep at least one administrator who does not come from the directory, so you can still sign in if the directory goes wrong.
User ledger
The ledger lists each directory user the bridge has seen, with
Email, Directory ID, Status,
Last seen and Actions. Until the first run it shows
“No user states yet”.
-
Narrow the list with
Search by email…or theStatusfilter, for exampleFlagged — neworConflict. -
Act on a row. A new user offers
InviteorClear flag; a conflict offersLinkorClear flag; a user flagged as removed offersReactivateorClear flag; a deactivated user offers onlyReactivate. An “Action applied” message confirms the change. -
Leave
Dry run (no writes)ticked, which it is by default, and selectSync now. A dry-run provisioning run is queued and writes nothing to users or invitations; it records only what it would have done. -
When the dry run's results look right, clear the box and select
Sync nowagain for a live run.
On a disabled connection the provisioning Sync now is unavailable,
as on the overview; pointing at it shows “Enable the connection to sync”.
Run history
Each run, scheduled or manual, appears with Started,
Status, Trigger (Scheduled or
Manual), Mode (Dry run or
Live), Results (provisioned, deactivated, flagged and
conflict counts) and Duration. Scheduled runs follow each completed
mirror sync of users, and only on connections with provisioning switched on.
Tips and limits
-
Provisioning has a dry run that writes nothing, and stops the destructive
part of a run that would change more users than its safety ratio allows. The
guard engages only above a minimum of ten users, and the run is then marked
Partial. - A local or single-sign-on administrator is never deactivated by a directory read: only users linked to that connection are.
-
Provisioning never creates an account with a password. It sends an
invitation, so the person confirms their email as any other new user would.
Directory users without a well-formed email address are not provisioned; the
ledger lists them as
Skipped. -
Start with
Flag for reviewand a dry run before choosingAuto-provisionorAuto-deactivate. -
On the Connectors board, the tile reads
Connectedonly once an enabled connection has completed a sync.
Where this connects
- Computer objects in the mirror feed the Active Directory import in the CMDB.
- Data-subject lookups in GDPR search the directory connections.
- For Entra snapshots of roles, devices and policies, see the Entra ID connector; for signing in with Entra, see Connect Microsoft Entra ID.
- Role mappings are explained in What each role can do, and the other integrations in Connectors.