Scim Client vs Server

Published
Length
3 min read

Luis Felipe Dias

All posts

In the scim client vs server model, the client sends user account updates. The server receives those requests and creates, updates, or deletes local accounts. Teams use a SCIM client inside their main identity system to manage staff roles. Teams build a SCIM server inside a target app to accept those changes. How the scim client vs server architecture works SCIM stands for System for Cross-domain Identity Management. It is an open standard that moves user data between systems. The protocol u

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

In the scim client vs server model, the client sends user account updates. The server receives those requests and creates, updates, or deletes local accounts.

Teams use a SCIM client inside their main identity system to manage staff roles. Teams build a SCIM server inside a target app to accept those changes.

How the scim client vs server architecture works

SCIM stands for System for Cross-domain Identity Management. It is an open standard that moves user data between systems. The protocol uses standard web requests and JSON objects to share user details.

The SCIM client is almost always your central identity provider. Tools like Okta, Microsoft Entra ID, and OneLogin act as the client. HR systems can also act as the client when new staff join.

The client watches for changes in your central staff directory. When an admin adds a person to a group, the client wakes up. It formats a web request with the user name, email, and role.

The client then sends that request across the network to the server. It uses standard HTTP verbs like POST, PUT, PATCH, and DELETE. Each verb tells the server what action to take on the account.

The SCIM server lives inside the target cloud app or internal tool. Slack, GitHub, and AWS Single Sign-On all run SCIM servers. If you build an enterprise SaaS app, you build the SCIM server.

The server listens on dedicated web endpoints for incoming client requests. It checks the bearer token or API key on every request. Once verified, the server updates its own database to match the client.

After the database change finishes, the server sends back a status code. This response tells the client that the user account is ready. The client records the server ID for that user for future updates.

Kubernetes API Server Access + K8s RBAC Role vs ClusterRole: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Where each role fits in your stack

Platform teams configure the SCIM client to automate staff onboarding and offboarding. Instead of making accounts by hand, admins assign groups in one place. The client pushes those group assignments out to every linked app.

App developers build a SCIM server to sell software to large companies. Enterprise buyers want to manage all user accounts from their central directory. Without a SCIM server, buyers must manage accounts in your app manually.

Both sides must agree on a shared user schema to work well. The standard defines core fields like work email, given name, and active status. Teams map directory fields on the client to database fields on the server.

Tradeoffs and runtime security boundaries

SCIM handles account creation and removal well, but it stops there. The protocol only runs when a user profile or group changes. It does not watch what a user does inside an active session.

Sync delays can also create security gaps during urgent offboarding. If a client fails to reach a server, an account stays active. Network errors or rate limits can delay account removal for minutes or hours.

Static group sync also encourages broad, standing permissions across your engineering stack. A developer pushed via SCIM often keeps database or server permissions all day. SCIM cannot approve a single query or mask emails and phone numbers.

To close this gap, teams pair SCIM account sync with runtime session controls. SCIM sets up the base user identity and team groups in advance. Runtime controls then check every live command and mask card numbers or national IDs.

Add runtime guardrails and masking beside your databases and APIs

Login rules, role grants, and CI checks govern who connects to your stack. Yet any allowed script, engineer, or AI agent still runs commands with the full scope of its role. For workloads on Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes, SSH, or internal HTTP services, hoop.dev sits beside the service as an open-source proxy, a sidecar for your database or API.

Before a query runs, hoop.dev guardrails check the statement against your rules. An AI Analyzer you configure can score intent or hold risky calls for human review. Next, hoop.dev data masking rewrites sensitive fields in responses, and each verdict is logged per listener. Explore the MIT-licensed project on GitHub.

Frequently asked questions

Is Okta a SCIM client or a SCIM server?

Okta acts primarily as a SCIM client when it pushes users to apps. It can also act as a server when an HR tool feeds it.

Does SCIM handle user log in and single sign-on?

No, SCIM only creates, updates, and deletes user records in the background. Protocols like SAML and OpenID Connect handle the actual log in flow.

Who starts the network request in SCIM?

The SCIM client always starts the request when directory data changes. The SCIM server never pulls data on its own; it only listens.

The query runs. The emails stay hidden.