← Integration Engineering
Integration Engineering

SSO and SCIM: The Two Questions Big Customers Will Ask

21 Oct 2026·3 min read

A bigger customer sends a security questionnaire. In it: "Do you support SSO and SCIM?" Both are integrations between your product and the customer’s identity provider, the system that holds their employees and logins, like Okta or Microsoft Entra ID.

SSO: log in with the company account

SSO means single sign-on. The user logs in on their company’s login page instead of making a new password for your product. Your product never sees the password. It gets a signed message from the identity provider. The two usual standards are SAML 2.0 and OpenID Connect (OIDC).

SCIM: who has an account

SSO only runs when someone logs in. It does not tell you when they leave. SCIM does. Your product runs a SCIM API, and the identity provider calls it to create, update and deactivate users. When a person leaves, Okta sets their "active" flag to false instead of deleting them. So treat "inactive" as "locked out now".

  • Together, a new hire gets access quickly, and a leaver loses it soon after IT turns off their company account.
  • Without them, someone at the customer adds and removes users by hand, and forgets some.
  • On deactivate, end their sessions and stop their API keys too. Locking the login page is not enough.
Do this in 60 secondsList every tool your team logs into with its own separate password. In those tools, someone who left could still have access today.
Today’s AI angleAI agents often act for a named employee, with that person’s tokens. Tie every agent credential to a real user, so when SCIM deactivates the person, their agent loses access too.
SSO and SCIM: The Two Questions Big Customers Will Ask · Ali Huzaifa