SCIM Deprovisioning: Why Disabling a User Must Also Revoke Live Access

An enterprise customer's offboarded employee can keep using a SaaS app after their identity provider account is disabled, because existing session cookies and personal API tokens remain valid. The article argues that SSO only blocks new logins and does not end current access, which is why enterprise customers request SCIM provisioning. It outlines the core SCIM endpoints an identity provider calls, such as creating, updating, and deactivating users via PATCH or DELETE requests. The author stresses that deactivation must block login, revoke all sessions, disable API tokens and pending invites, and log the change in one transaction-safe step. The piece also recommends issuing a separate, hashed bearer token per tenant so each token can only affect its own tenant's users.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in