Skip to content
BENIBIX Learn

System for Cross-domain Identity Management (SCIM)

Development🔑 AuthIdentity Management

Also known as SCIM, SCIM 2.0, SCIM Provisioning, User Provisioning

A standard that keeps user accounts in step across many apps. It does not log you in.

Think of it like

Think of it like a class list sent to every club. When a kid joins or leaves, each club's list changes too.

Example

Jack leaves his job on Friday. IT turns off his account in the identity provider, and SCIM turns off his Slack and Zoom accounts too.

Why it matters

Without it, someone adds and removes accounts in each app by hand. One missed app leaves a past worker with a way back in.

Definition

SCIM is a standard for keeping user accounts the same across many apps. The identity provider sends each app a message when someone joins, changes or leaves. The app then makes, updates or turns off that account. The messages are plain web requests with JSON inside. SCIM never logs anyone in; it only keeps the lists of users and groups in step. Version 2.0 came out in 2015.

Example code

http
POST /scim/v2/Users HTTP/1.1
Content-Type: application/scim+json

{
  "schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
  "userName": "jack@example.com",
  "active": true
}
The login service asks the app to make a new account for Jack.
SCIM is the bottom lane. It runs ahead of time, so each app's user list is right.

Common mistake

Thinking single sign-on also removes accounts. It only stops the next login. The account, and any token it holds, stays until SCIM or a person removes it.

Key takeaways

  1. 1
    Join, move, leave. Accounts follow the staff list.
  2. 2
    Plain web requests. JSON sent to the Users and Groups paths.
  3. 3
    Not a login. It never signs anyone in.

Compare