Home / Companies / WorkOS / Blog / Post Details
Content Deep Dive

SCIM directory sync: A deep dive into deprovisioning

Blog post from WorkOS

Post Details
Company
Date Published
Author
Maria Paktiti
Word Count
2,538
Company Posts That Month
60
Language
English
Hacker News Points
-
Post removed?
No
Summary

Reliable employee deprovisioning is a security and audit-critical challenge because terminations often arrive as soft deactivations rather than deletes, identity providers implement SCIM PATCH operations differently, and authoritative HR or directory systems may rely on APIs, polling, or scheduled file transfers instead of SCIM. WorkOS Directory Sync presents these varied inputs through normalized directory, user, and group events, with user deletion events retaining whether the person was inactive or merely unassigned, while stable external IDs rather than mutable emails should be used for reconciliation and reactivation. Effective implementations must revoke active sessions, OAuth tokens, API keys, cached permissions, and account access rather than simply change a database flag, while accounting for latency from identity-provider sync cycles and JWT expiration. The recommended approach treats event streams as a latency optimization backed by scheduled full reconciliation, makes all update paths idempotent, defines source-of-truth priorities for conflicting systems, and retains inactive user records with timestamps and reasons. Detailed append-only audit logs and SCIM request logs provide evidence of what was received and revoked, helping organizations investigate missed events and satisfy access-removal audits, while managed directory-sync services reduce the burden of maintaining provider-specific connectors, normalization, polling, and debugging.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Platform Engineering 9 1,691 347 96 +40%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.