
Argent with Keycloak
Argent Strategic Intelligence reads users and groups from a Keycloak realm, so every AI agent answers to a real, active person. Keycloak can also be your single sign-on for the Argent console.
What Argent does with Keycloak
Keycloak holds your realm's people. Argent reads them through the Keycloak Admin REST API and uses them as the owners of your AI agents.
- People, groups and memberships. Argent pulls them from Keycloak, together with each person's state (active, suspended, deprovisioned).
- 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 Keycloak 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 Keycloak 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. Keycloak groups map onto Argent grants under Access, versioned, so access follows the directory instead of hand-made lists.
- Single sign-on as well. Keycloak can sign people in to the Argent console over OpenID Connect or SAML 2.0; both were proven live with Keycloak.
- Or push over SCIM. Keycloak can also send people to Argent's SCIM 2.0 endpoint with the
keycloakdialect.
How it connects
A read-only pull. Argent reads from Keycloak on a schedule; nothing in Keycloak is changed.
- In the Argent console, open Integrations, Identity sources and choose Add connector, type Keycloak.
- Give it a display name and enter the settings below.
- Connect, then Test: Argent pulls a sample from Keycloak to prove the link works end to end.
- Open Attribute mapping, run the mapper, review the proposal and save it. Saving the first mapping version turns the connector on.
- Check the result under Identities, People: each person shows KEYCLOAK as their source.
What you configure
| Setting | What to enter |
|---|---|
| Base URL | Your Keycloak server, for example https://sso.yourcompany.com. |
| Realm | The realm whose users Argent reads. |
| How Argent reads Keycloak | Either a client with the client-credentials grant (client ID plus a secret in your vault) or an admin user whose password sits in your vault. Token realm defaults to master, client ID to admin-cli. |
| Page size | Optional. Default 100. |
Argent keys each person on Keycloak's own server id, never the username or email.
- 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.
When someone leaves, their agents stop
Argent does not have to wait for Keycloak to send an event. On its next check it compares who is still active with the people it holds.
- Switched off in Argent. A person who is missing from Keycloak, or switched off there, is deactivated in Argent. The change is signed into the audit record in the same step.
- 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.
- Access removed. Their access in Argent is removed in the same transaction, so nothing they were granted lingers.
- 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.
Where it fits in Argent
- Capabilities: Identity Tethering, Owner Offboarding, Keyless Agents, One-Click Audit Evidence.
- Goals: agent identity and ownership, audit and accountability, compliance evidence.
- Use cases: securing AI coding agents, rolling out copilots and chat safely, AI in regulated and air-gapped environments.
- Start in watch mode. Argent can record what it would have done before it enforces anything. See Watch Before You Enforce.
- See it run: take the walkthrough, browse all integrations, or book a demo.
Want this running on your own use cases?
Book a demoKeycloak and the other identity vendors Argent connects to. Open any logo for its page. SailPoint's mark opens IdentityIQ. Also see SailPoint Identity Security Cloud.