Integration: LDAP and Active Directory

Argent with LDAP and Active Directory

Argent Strategic Intelligence reads users and groups from Active Directory or any LDAP directory, so every AI agent answers to a real, active person, and leavers take their agents with them.

01 / INTEGRATION: LDAP AND ACTIVE DIRECTORY

What Argent does with your directory

Most companies still keep their people in Active Directory or another LDAP directory. Argent reads it, read-only, and uses it as the list of people who may own AI agents.

  • People, groups and memberships, read from your directory.
  • An owner for every agent. Every agent registered with Argent must have an active human owner, and Argent checks that owner on every request. People from your directory are those owners. See Identity Tethering.
  • No owner, no answer. A request from an agent whose owner is missing or switched off is refused, and nothing reaches the AI model.
  • Attribute mapping, reviewed by a person. Argent reads the fields your directory exposes and proposes how they map onto Argent's (who is who, email, status, department). An admin reviews it, edits it and saves it as a new version; earlier versions stay on record.
  • Groups become access. Your directory groups map onto Argent grants under Access, versioned, so access follows the directory instead of hand-made lists.
02 / INTEGRATION: LDAP AND ACTIVE DIRECTORY

How it connects

A read-only pull. Argent reads from your directory on a schedule; nothing in your directory is changed.

  1. In the Argent console, open Integrations, Identity sources and choose Add connector, type LDAP.
  2. Give it a display name and enter the settings below.
  3. Connect, then Test: Argent pulls a sample from your directory to prove the link works end to end.
  4. Open Attribute mapping, run the mapper, review the proposal and save it. Saving the first mapping version turns the connector on.
  5. Check the result under Identities, People: each person shows LDAP as their source.
03 / INTEGRATION: LDAP AND ACTIVE DIRECTORY

What you configure

SettingWhat to enter
URLldaps://dc.yourcompany.com:636 (TLS) or ldap://.... Only the ldap and ldaps schemes are accepted.
Bind DNThe read-only service account Argent binds as.
Bind passwordStored in your vault; Argent is given only its path.
Base DNWhere Argent starts reading, for example ou=People,dc=yourcompany,dc=com.
Filter and page sizeOptional: narrow the search with an LDAP filter; large directories are read page by page.

The mapper proposes which attribute is the login and the email. For Active Directory, use a filter that leaves out disabled accounts, for example (&(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2))), so a disabled account drops out on the next check.

  • The secret stays in your vault. Argent's configuration holds only the vault path of the credential, never the credential itself. Argent works with HashiCorp Vault and OpenBao, AWS Secrets Manager, CyberArk Conjur and Infisical.
  • Guarded dial-out. Every identity connector dials out through a guarded client that refuses private, loopback, link-local and cloud-metadata addresses. Turn on the egress allowlist and only the addresses you list are reachable. A directory, database or Keycloak server on your private network is reached by listing its private address range in the deployment's tenant private-range setting; cloud-metadata addresses stay refused whatever is listed.
04 / INTEGRATION: LDAP AND ACTIVE DIRECTORY

When someone leaves, their agents stop

Argent does not have to wait for your directory to send an event. On its next check it compares who is still active with the people it holds.

  1. Switched off in Argent. A person who no longer appears in your directory search is deactivated in Argent. The change is signed into the audit record in the same step.
  2. Their agents are held. The keys of every agent that person owns are held, and each request from those agents is refused before it reaches a model.
  3. Access removed. Their access in Argent is removed in the same transaction, so nothing they were granted lingers.
  4. Your hand decision sticks. A person an admin switched off by hand stays off, even if a later directory sync reports them active. Only an admin can turn them back on.

A leaver is not deleted. Their agents are refused, held and kept on the record until an admin hands them to a new owner. See Owner Offboarding.

05 / INTEGRATION: LDAP AND ACTIVE DIRECTORY

Where it fits in Argent

Identity sources Argent connects to

The vendors with their own page in this group. Open any logo for its page. SailPoint's mark opens IdentityIQ. Also see SailPoint Identity Security Cloud.

  • Okta
  • Microsoft Entra ID
  • Auth0
  • Keycloak
  • SailPoint
  • Saviynt
  • Ping Identity