SCIM: Definition, How It Works, and Limitations

Access & IdentitiesAlso known as: SCIM, System for Cross-domain Identity Management, SCIM 2.0, SCIM Provisioning
In brief

SCIM (System for Cross-domain Identity Management, currently SCIM 2.0) is an open IETF standard that allows systems to create, update, query, and remove user accounts and groups via a uniform REST API using JSON. SCIM is specified in RFC 7643 (core schema) and RFC 7644 (protocol) and is primarily used for automated provisioning in SaaS applications.

Key Takeaways

  • SCIM 2.0 is defined in IETF RFC 7643 and RFC 7644 from 2015.
  • SCIM uses HTTP methods such as GET, POST, PUT, PATCH, and DELETE with JSON.
  • SCIM governs account provisioning, not authentication.
  • Many SaaS providers only offer SCIM on higher pricing tiers.

How does SCIM work?

SCIM connects a source system, the SCIM client, with a target application, the SCIM service provider.

  • The client, usually an identity provider like Microsoft Entra ID, detects a change.
  • It sends an HTTP request with JSON to the application's SCIM endpoint.
  • The application creates the account, updates attributes, or deactivates it.
  • Groups are transferred in the same way and control roles within the application.

What is the difference between SCIM and SSO?

SCIM creates and removes accounts, whereas Single Sign-On only governs logging in to existing accounts. The two complement each other: SAML or OpenID Connect handle login, while SCIM ensures that the matching account with the right groups exists and is deactivated upon departure.

What are the limitations of SCIM?

SCIM only works for applications that support the standard and are connected.

  • Many applications offer SCIM only on Enterprise tiers.
  • Implementations vary; not all attributes or groups are supported everywhere.
  • Accounts outside the identity provider, such as self-adopted tools, remain untouched.
  • SCIM does not handle licenses, data handovers, or offboarding tasks.

Example: SCIM, System for Cross-domain Identity Management in practice

Real-world example

Example: A logistics company with 90 employees connects 6 SaaS applications to Microsoft Entra ID via SCIM. When a dispatcher joins, Entra ID automatically creates her account in all 6 applications with the Dispatch group. When she leaves, Entra ID deactivates the 6 accounts. 9 additional applications without SCIM are handled manually by the tool admins.

SCIM, System for Cross-domain Identity Management vs. Single Sign-On (SSO)

AspectSCIM, System for Cross-domain Identity ManagementSingle Sign-On (SSO)
PurposeCreate, update, and deactivate accounts and groupsLog in with a central identity
StandardsSCIM 2.0 under RFC 7643 and RFC 7644SAML 2.0, OpenID Connect
TimingUpon onboarding, change, or departureAt every login
Without the otherAccount exists; login uses a separate passwordLogin works; account must be created separately

SCIM ensures that an account exists and stays up to date, whereas Single Sign-On ensures that the person can log in to it via the identity provider.

How does Sovaro help with SCIM, System for Cross-domain Identity Management?

How Sovaro helps

Sovaro is not a SCIM provisioner and does not provide a SCIM interface for creating accounts in third-party applications. A new hire or departure in Personio, Google Workspace, or Microsoft Entra starts a workflow in Sovaro with tasks for tool admins. Sovaro detects apps via its agent and browser extension, including those not connected via SCIM or SSO.

Frequently Asked Questions about SCIM, System for Cross-domain Identity Management

Sources

See Sovaro with your own data.

Connect Google Workspace or Microsoft Entra, share the setup link, and see devices, apps, and licenses per person in one place.

14-day free trial, no payment details required. Cancel monthly.