SCIM
System for Cross-domain Identity Management: a standard HTTP and JSON protocol an identity provider uses to create, update and deactivate user accounts and groups in other apps.
Single sign-onSSO: Single sign-on: people sign in once with their organization's identity provider and reach many apps without a separate password for each. answers "who is signing in right now?". It says nothing when someone leaves the company: their account in each app stays, and sessions or API keys already issued there can keep working. SCIM fills that gap. The identity provider (the SCIM client) pushes changes to each app (the service provider) as they happen: a new hire gets an account, a team change updates a group, a leaver is deactivated the same day.SCIM 2.0 is specified in two IETF RFCs from 2015. RFC 7643 defines the schema: a core User (urn:ietf:params:scim:schemas:core:2.0:User) with attributes such as userName, emails and active, a Group with members, and an enterprise extension. RFC 7644 defines the protocol: JSON over HTTP (application/scim+json) on endpoints such as /Users, /Groups, /Schemas and /ServiceProviderConfig, with POST to create, GET with filters to search, PUT to replace, PATCH to change part of a resource, and DELETE.
Two identifiers matter. The service provider assigns id, and the client must not set it. The client may send externalId, its own id for the person, so both sides can match records later.
Example
An employee leaves. The identity provider looks the user up and deactivates them:
GET /scim/v2/Users?filter=userName eq "jo@example.org"
PATCH /scim/v2/Users/2819c223
Content-Type: application/scim+json
{ "schemas": ["urn:ietf:params:scim:api:messages:2.0:PatchOp"],
"Operations": [ { "op": "replace", "path": "active", "value": false } ] }The app can then end the account's sessions and keys at once, without waiting for anyone to notice.
Common confusion
- SCIM is not sign-in. It moves account data; it never authenticates a user. Apps usually run SCIM next to OIDC or SAML, not instead of them.
- Just-in-time provisioning is not SCIM. Creating an account on first SSO sign-in covers joiners, but not leavers or role changes between sign-ins.
active: falseis not always deletion. RFC 7643 callsactivethe user's "administrative status" and leaves its exact meaning to the service provider. Many apps deactivate and keep the record for audit.
In L2M
For how people get accounts and roles in L2M, see OIDC single sign-on, group-to-role mappings, user invites and service accounts.
Further reading
- RFC 7643: SCIM core schema (IETF)
- RFC 7644: SCIM protocol (IETF)