SCIM
An open standard protocol (based on RFC 7644) for automating cross-domain user identity management. It uses standardized REST APIs to synchronize user creation, updates, and deletion between identity providers and service providers, serving as the de facto standard for enterprise SaaS identity governance.
Core Facts
SCIM is the System for Cross-domain Identity Management, which plays a core role in automated user provisioning.
SCIM (System for Cross-domain Identity Management) is an open standard for automating the exchange of user identity information.
SCIM 2.0 is a user directory synchronization protocol standardized by the IETF that defines a RESTful API specification for automating user lifecycle management between IdPs and applications.
Timeline (last 90 days)
Directory sync uses the SCIM protocol to automatically push user and group information from enterprise directories (such as Okta and Azure AD) to SaaS products.
Compared with traditional directory protocols such as LDAP, SCIM is based on REST/JSON and is better suited to the modern SaaS ecosystem.
SCIM is an open identity management standard developed by the IETF and defined by RFC 7642/7643/7644.
Whether Alter can integrate with mainstream IdPs via standard protocols such as SAML, OIDC, or SCIM, and reuse enterprises' existing group and role definitions, will directly determine whether it can enter the procurement lists of mid-to-large enterprises.
WorkOS's Directory Sync feature connects to enterprise identity providers (such as Okta, Azure AD and Google Workspace) via the SCIM protocol.
Membership change events are generated on the Directory Sync path: group changes on the IdP side are pushed via SCIM, triggering WorkOS to update organization membership, which is then written to the audit log.
If SCIM synchronization is event-driven, deprovisioning on departure can take effect within minutes; if periodic synchronization is used, the interval may range from several hours to a day.
SCIM's coverage depends on whether an application supports the protocol, and not all applications provide a SCIM interface.
SCIM's `active` attribute is the key switch for deprovisioning on departure; setting it to false triggers account disabling on the application side.
SSO and SCIM are not substitutes but complementary pillars of identity management.
40 more timeline events
All Facts (20)
SCIM is the System for Cross-domain Identity Management, which plays a core role in automated user provisioning.
75%VerifiedSCIM (System for Cross-domain Identity Management) is an open standard for automating the exchange of user identity information.
65%VerifiedSCIM 2.0 is a user directory synchronization protocol standardized by the IETF that defines a RESTful API specification for automating user lifecycle management between IdPs and applications.
65%VerifiedSCIM (System for Cross-domain Identity Management) is currently at version 2.0 and is an IETF-standardized user directory synchronization protocol
65%VerifiedWorkOS is a technology company focused on providing enterprise-grade identity authentication and user management infrastructure for SaaS applications, with products covering core enterprise IT capabilities such as SSO (Single Sign-On), SCIM directory synchronization, and audit logs.
65%UnverifiedDirectory sync uses the SCIM protocol to automatically push user and group information from enterprise directories (such as Okta and Azure AD) to SaaS products.
50%UnverifiedCompared with traditional directory protocols such as LDAP, SCIM is based on REST/JSON and is better suited to the modern SaaS ecosystem.
50%UnverifiedSCIM is an open identity management standard developed by the IETF and defined by RFC 7642/7643/7644.
50%UnverifiedMembership change events are generated on the Directory Sync path: group changes on the IdP side are pushed via SCIM, triggering WorkOS to update organization membership, which is then written to the audit log.
50%UnverifiedWorkOS's Directory Sync feature connects to enterprise identity providers (such as Okta, Azure AD and Google Workspace) via the SCIM protocol.
50%UnverifiedIf SCIM synchronization is event-driven, deprovisioning on departure can take effect within minutes; if periodic synchronization is used, the interval may range from several hours to a day.
50%UnverifiedSCIM's `active` attribute is the key switch for deprovisioning on departure; setting it to false triggers account disabling on the application side.
50%UnverifiedSCIM's coverage depends on whether an application supports the protocol, and not all applications provide a SCIM interface.
50%UnverifiedSSO and SCIM are not substitutes but complementary pillars of identity management.
50%UnverifiedSCIM is usually used together with SAML/OIDC: the latter handles authentication, while the former handles provisioning.
50%UnverifiedSCIM is a RESTful protocol standardized by the IETF, and the current mainstream version is SCIM 2.0 (RFC 7642/7643/7644).
50%UnverifiedWhen evaluating a SCIM solution, the vendor's specific trigger conditions should be confirmed, such as departure events bound to the HR system, directory group membership changes, or fixed-interval polling.
50%UnverifiedSCIM synchronization logs and SSO login records can serve as indirect evidence, but they cannot replace the authoritative data source within the application.
50%UnverifiedDistinguishing between "direct adjustment within the application" and "indirect triggering via IdP or automation" during remediation is essentially a trade-off between immediacy and auditability: manual adjustments are fast but error-prone and hard to trace, while changes triggered via IdP group mapping or SCIM are more consistent but depend on the quality of prior integration.
50%UnverifiedSCIM is an open standard protocol used to automatically synchronize user and group information between identity providers and business applications.
50%