SCIM Sandbox gives you a live SCIM 2.0 server and three tools around it:
SCIM Server Manager for workspaces and tokens,
SCIM Compliance for conformance runs, and
SCIM Playground for hand-crafted SCIM requests. Test identity
provisioning flows end to end without building the platform from scratch.
Go from zero to a working SCIM endpoint in minutes.
Start in SCIM Server Manager, create a workspace, and generate a token. Then run a
conformance check in SCIM Compliance, and use SCIM Playground to send individual
SCIM requests against the endpoint you just created.
Click a step to open its instructions and screenshot, or use the arrows at the bottom of each step.
Sign up with an email address so your workspaces and validation runs stay tied to your user.
You only need to register once. After that, the same account can be reused whenever you come back to inspect traffic or run more validation passes.
Step 03
Log in
Return to SCIM Server Manager and sign in to create and manage your sandbox data.
Once authenticated, the UI becomes the fastest path to creating fresh endpoints and checking the state of your isolated test environments.
Step 04
Create a workspace
Use the workspace list to create an isolated sandbox for your SCIM tests and sample data.
Each workspace gives you a clean testing boundary, which makes it easier to compare clients, reproduce provisioning problems, and delete old experiments safely.
Step 05
Open the workspace to retrieve the URL and create access tokens
Copy the base URL, create access tokens, and use the built-in generators to seed users, groups, and relationships.
This is the handoff point for client testing: your SCIM base URL and bearer token are what provisioning clients, SCIM Compliance, and SCIM Playground all use next.
Step 06
Run a compliance check
Paste the base URL and token into SCIM Compliance and run the conformance suite against your endpoint.
Each run reports pass/fail counts across the RFC 7643 and RFC 7644 surface, and the run detail view shows exactly which assertions failed. Results are kept so you can compare runs after a change.
Open SCIM Playground to build individual SCIM requests against the same endpoint and read the raw responses.
Filters, projections, PATCH bodies, bulk operations, .search, and ETag concurrency are all reachable from the request builder. This is where you reproduce a client’s exact call and see what the server actually returns.
SCIM Sandbox is split into repositories that map cleanly to runtime roles:
the SCIM server, the compliance and playground tooling, infrastructure, and policy.
Privacy and terms are published separately from the runtime services so the public site can link to
clear, stable legal pages without mixing that content into the product flows.
Privacy policy
Read how the sandbox stores data, what it is intended for, and the development-only constraints around request payload retention.