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

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:

No screenshot of this screen was captured for this edition of the guide.

Create a connection

  1. Select New connection. A dialog titled New AD/LDAP connection opens with Name and Type, set to LDAP.
  2. Enter a Name. Create connection stays unavailable until the name has text in it.
  3. For an LDAP directory, fill in LDAP URL, Base DN (where in the directory to start reading), Bind DN (the read account) and Bind 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.
  4. For Entra ID, set Type to Microsoft Entra ID. The box Use the signed-in Microsoft integration (no client secret needed) is ticked. Clear it to enter a Client ID, Client secret and Tenant ID instead.
  5. 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.
If you already use the Entra ID connector

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.

  1. Select Edit. The card turns into a form in the page (not a dialog) with Name and, for LDAP, LDAP URL, Base DN, Bind DN, Bind password and Search filter (optional). Below them are the boxes Enabled, Sync users, Sync groups and Sync computers.
  2. Leave Bind password blank to keep the stored password; it is never shown. Select Save changes. A “Connection updated” message appears and the card returns. Cancel discards the edit.
  3. 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.
  4. Select Sync now to refresh the mirror straight away. The button reads Syncing... 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”.
  5. 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

  1. Select Add mapping. A form opens with Group (DN or GUID), Aegis role, Priority and Active.
  2. 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 columns Group, Role, Priority, Active and Actions.
  3. Use Edit or Delete on a row. Deleting asks for confirmation; members fall back to the default role on the next run.
Warning: mapping a group to Admin

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”.

  1. Narrow the list with Search by email… or the Status filter, for example Flagged — new or Conflict.
  2. Act on a row. A new user offers Invite or Clear flag; a conflict offers Link or Clear flag; a user flagged as removed offers Reactivate or Clear flag; a deactivated user offers only Reactivate. An “Action applied” message confirms the change.
  3. Leave Dry run (no writes) ticked, which it is by default, and select Sync now. A dry-run provisioning run is queued and writes nothing to users or invitations; it records only what it would have done.
  4. When the dry run's results look right, clear the box and select Sync now again 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

Where this connects