Info
More information about user provisioning and user authentication with Asset can be found via the general User provisioning and authentication article.
General
The System for Cross-domain Identity Management (SCIM) API is an open-standard protocol designed to simplify the management of user identities across multiple platforms. It provides a standardized schema and RESTful API for performing CRUD (Create, Read, Update, Delete) operations on user and group resources. SCIM is widely used for automating user provisioning and deprovisioning in cloud-based applications.
Key Features of SCIM API
SCIM enables seamless integration between identity providers (e.g., Microsoft Entra ID, Okta) and service providers (e.g., SaaS applications). It uses JSON for data representation and REST APIs for communication. The core functionalities include:
- User Provisioning: Automatically create, update, or delete user accounts in connected applications.
- Group Management: Manage group memberships and permissions.
- Synchronization: Keep user attributes and group memberships consistent across systems.
- Deprovisioning: Automatically deactivate or delete user accounts when employees leave an organization.
Benefits of SCIM API
SCIM offers several advantages for organizations and developers:
- Automation: Reduces manual effort by automating user lifecycle management.
- Consistency: Ensures data consistency across multiple systems.
- Security: Enhances security by quickly deactivating accounts and enforcing access controls.
- Scalability: Supports large-scale user and group management for growing organizations.
- Interoperability: Simplifies integration with pre-existing identity providers and applications.
User Story
As an IT administrator, I want to automatically provision, update, and deprovision user accounts in Asset using SCIM, so that I can reduce manual work, ensure data consistency, and maintain compliance with company security policies.
Implementation guides
For the complete end-to-end implementation, multiple steps and applications need to be set-up (Asset, the Integration Platform and the Identity Provider (e.g. Microsoft Entra ID (former Azure AD))) to enable the SCIM integration. These guides can be found in the following articles:
- Azure configuration guide for SCIM: Done by the customer
- Asset configuration guide for SCIM: Done by the implementation consultant