Integration: SAML 2.0 SSO

Argent with SAML 2.0 SSO

Your people sign in to the Argent console with the SAML identity provider they already use. Argent Strategic Intelligence checks every assertion, and was proven live with Keycloak and Microsoft Entra ID.

01 / INTEGRATION: SAML 2.0 SSO

What Argent does with SAML 2.0

The same console sign-in as OpenID Connect, over the SAML wire many enterprises still standardize on.

  • One provider per tenant. Switching a tenant between SAML and OpenID Connect is one setting.
  • 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.

SAML 2.0 is the OASIS standard for exchanging sign-in assertions.

02 / INTEGRATION: SAML 2.0 SSO

Every assertion is checked

A response that fails any check is refused and never becomes a session.

  • Signature, audience, recipient, destination and the reply-to (InResponseTo) are all enforced, with a two-minute clock allowance.
  • A response cannot be reused: the relay state is single use.
  • A denied sign-in is signed into the audit record with its reason code, for example sso.saml.invalid_signature or sso.saml.replay.
  • Argent fetches your provider's metadata through its address guard, so a metadata URL pointing at an internal or cloud-metadata address is refused.

In the live proof, a tampered Keycloak assertion and an Entra assertion altered in flight were both refused, and both refusals were signed.

03 / INTEGRATION: SAML 2.0 SSO

What you configure

SettingWhat to enter
Entity ID (give to your provider)https://<your Argent host>/v1/sso/saml/metadata. The metadata URL is public, so most providers can import it directly.
ACS URL (HTTP-POST)https://<your Argent host>/v1/sso/saml/acs
NameIDUnspecified or persistent; Argent stores it as the subject. Transient is refused.
Your provider's metadataIts metadata URL, or the XML pasted in. When your provider rotates its signing certificate, save the provider again so Argent takes the new one.
Email attributeDefaults to the standard emailaddress claim; set another attribute name if your provider sends email elsewhere.
Request signingOptional: give Argent a key and certificate and its sign-in requests are signed and the certificate is published in its metadata.
04 / INTEGRATION: SAML 2.0 SSO

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