Automated push-based identity provisioning (RFC 7643 & RFC 7644). The identity provider (Entra ID, Okta, etc.) monitors employee lifecycle changes and pushes user/group events to your SCIM endpoint in real time. This page acts as that target service provider and exposes every incoming raw payload.
Unlike SAML or OIDC (which authenticate users at login time), SCIM handles identity lifecycle management in the background: accounts are provisioned before users ever attempt to log in, and deprovisioned immediately when they leave. Here is the standard protocol sequence:
GET /ServiceProviderConfig,
GET /Schemas, and GET /ResourceTypes to discover which capabilities
the server supports (e.g., authentication schemes, maximum filter results, bulk limits, and PATCH support).
GET /Users?filter=userName eq "john@example.com".
If the user does not exist (totalResults: 0), it moves to creation. If the user already exists,
the IdP captures the server's id to synchronize attributes rather than producing a duplicate.
POST /Users with the standardized SCIM JSON payload (names, emails, active status,
and optional enterprise extensions like department or manager). The server creates the identity and returns
HTTP 201 Created with a server-generated unique id.
PATCH /Users/{id} containing fine-grained Operations
(e.g., replace: {"title": "Staff Engineer"}).
POST /Groups, and members are added or removed dynamically using
PATCH /Groups/{id} by referencing each user's SCIM id.
PATCH /Users/{id} with active: false. If hard deletion is configured,
it subsequently sends DELETE /Users/{id}.
Authorization: Bearer <token> header. Passwords sent during creation are masked in the
audit log and never written to persistent storage.
Generate an isolated, private SCIM 2.0 server instance. The generator provisions a unique endpoint identifier (EID) and an unguessable 256-bit cryptographic bearer token.
Copy these credentials into your identity provider (e.g. Entra ID Enterprise Application Provisioning settings). Requests sent to this URL with this Secret Token will be routed to your private serverless partition.
/Users, /Groups) reside.localStorage) so this session survives page reloads.Configure an Enterprise Application in Microsoft Entra to push identities to your new endpoint:
GET /Users?filter=...) to verify reachability.
Manual Testing: If you don't have access to an Entra tenant right now, execute this curl command in your terminal to simulate an identity provider pushing a newly created user:
// Create an endpoint first
Real-time audit log of all inbound SCIM requests received by your endpoint (newest first). Click any request row to inspect the exact HTTP headers, payload schemas, and response status returned by the server.
This view represents the target application's local identity database. As Entra ID processes lifecycle events,
the server maintains the correlation between the IdP's source directory object ID (externalId)
and this Service Provider's internal primary key (id).
Click any user or group row to view its complete SCIM 2.0 JSON document.