Intermediate LevelAuthentication & Authorization
What is SCIM (System for Cross-domain Identity Management) 2.0 protocol?
❓ Interview Prompt: Explain SCIM 2.0 REST protocol (RFC 7643/7644), automated user provisioning, deprivisioning, and Okta/Azure AD sync.
While SAML/OIDC handle user authentication, SCIM 2.0 (System for Cross-Domain Identity Management) (RFC 7643 & 7644) automates user identity lifecycle provisioning and de-provisioning.
Why SCIM is Essential:
Without SCIM, when an employee leaves an enterprise, admins must manually delete their account across 50 different SaaS tools. With SCIM:
1
Admin deactivates user in Okta / Azure AD.
2
Okta automatically dispatches a 'DELETE /Users/{id}' or 'PATCH /Users/{id}' ('active: false') HTTP request to all connected SaaS REST API endpoints.
3
SaaS backends deactivate user accounts instantly!
Code Implementation Example
json
{
"schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
"id": "2819891",
"userName": "alice@company.com",
"name": { "givenName": "Alice", "familyName": "Smith" },
"emails": [{ "value": "alice@company.com", "primary": true }],
"active": true
}💡Standardized SCIM 2.0 User resource JSON schema representation.
🎯 Interview Key Takeaway
SCIM 2.0 is a standardized REST API specification for automating real-time user provisioning and de-provisioning from Identity Providers.
#SCIM#Provisioning#REST API#Enterprise#Intermediate
Back to all Authentication & Authorization Questions→