
Argent with OpenID Connect SSO
Your people sign in to the Argent console and owner portal with the identity provider they already use. Argent Strategic Intelligence speaks OpenID Connect, proven live with Keycloak and Microsoft Entra ID.
What Argent does with OpenID Connect
One login for your people: the console for admins and auditors, the owner portal for the people who own agents, and the command-line device login through the portal.
- Per tenant. Each tenant sets its own provider. At sign-in a person types the organization's short name and is sent to that provider.
- Linked to a person who already exists. Sign-in does not invent accounts by default. The first time, Argent links the sign-in to the one person in your tenant with that verified email; after that the link follows the provider's subject, so a later email change does not move the account.
- Groups to roles. Map provider groups to the Auditor or TenantAdmin role. On every sign-in the account takes the highest mapped role, and a role managed this way cannot be raised by hand.
- Optional auto-provision. Off by default. Turned on, an unknown user with a verified email gets a person and a console account in one step, signed.
- Optional SSO only. Turned on, passkey sign-in is refused for the tenant's people. A platform administrator's passkey stays as the break-glass way in, and every such sign-in is signed.
- Passkey step-up stays. Sensitive changes still ask for a fresh passkey, whatever the sign-in method. See Passkeys.
- Signed record. Every sign-in, link, refusal and settings change is a signed audit fact; and in those facts the email and subject appear only as hashes.
Works with standards-compliant OpenID Connect providers that sign ID tokens with RS256, and is proven live with Keycloak and Microsoft Entra ID.
How it connects
Authorization code with PKCE, checked end to end.
- The browser goes to your provider with a code challenge (PKCE S256, RFC 7636), a single-use state and a nonce.
- Your provider sends it back to
https://<your Argent host>/v1/sso/callback. - Argent checks the ID token: signature from your provider's published keys, issuer, audience, expiry, issue time and nonce (for Entra, the directory id as well).
- The session is written only after the sign-in is signed into the audit record. If the record cannot be written, the sign-in is refused.
- The issuer must be https, and every endpoint in its discovery document must sit on the issuer's own address, so a hostile document cannot redirect the code or the secret.
- A failed sign-in returns one plain reason (unavailable, failed or unlinked) and never says which check failed.
What you configure
| Setting | What to enter |
|---|---|
| At your provider | A confidential client with redirect URI https://<your Argent host>/v1/sso/callback and scopes openid profile email. |
| Issuer | Your provider's issuer URL (https). Argent reads its discovery document before it saves. |
| Client ID and secret | The secret is write-only: Argent stores it in its platform vault under your tenant and never returns it. |
| Microsoft Entra ID | Add the optional ID-token claims email and xms_edov, and make sure each user's mail attribute is set. |
| Your people | Each person who signs in exists in the tenant with the email the provider asserts, and holds a console account if they need the console. |
Where it fits in Argent
- Capabilities: Identity Tethering, Owner Offboarding, One-Click Audit Evidence.
- Goals: agent identity and ownership, audit and accountability, compliance evidence.
- Other sign-in options: SAML 2.0, Passkeys. Provisioning: SCIM 2.0.
- 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 demoThe 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.