WSO2 is now Choreo LabsLearn more

Trusted AI Governance
Build

Create agents and AI apps with the tools and languages your teams already use.

Connect

Link agents securely to your APIs, data, models and business systems.

Run

Deploy, observe and operate agents and AI apps reliably at any scale.

Govern

Control identity, access, cost and policy for every agent in production.

Agent Management

Developer Platform

  • API Management Cloud

    Design, secure and publish APIs with governance and analytics built in.

    Sign Up Now
  • Integration Cloud

    Connect apps, data and AI agents with low-code and pro-code integration.

    Sign Up Now
  • Identity & Access Management Cloud

    Secure sign-in and access for customers, partners, workforce and agents.

    Sign Up Now
  • Agent Management Cloud

    Build, run and govern AI agents with full visibility and control.

    Sign Up Now
  • Developer Platform Cloud

    Ship cloud-native apps faster on an internal developer platform.

    Sign Up Now

Self-Hosted

Full control over your stack. Deploy directly to your own servers, bare metal, cloud, or Kubernetes environment. Your data never leaves your perimeter.

Product Downloads
Choreo Labs
AI Governance
Platform
Solutions
Resources
Blog

Introduction to system for cross-domain identity management (SCIM)

Image credits: cottonbro from Pexels

What is SCIM?

Over the last few years, the world has been moving from on-premises to cloud-based environments. In this migration process, identity provisioning becomes a critical factor due to confidentiality concerns and the security of user data. The System for Cross-domain Identity Management (SCIM) specification is designed as an open standard for managing user identity in cloud-based applications and services easier, faster, and cheaper. This specification suite seeks to build upon experience with existing schemas and deployments, placing specific emphasis on the simplicity of development and integration while applying existing authentication, authorization, and privacy models.

According to the rfc7642 specification:

The System for Cross-domain Identity Management (SCIM) specification is designed to manage user identity in cloud-based applications and services in a standardized way to enable interoperability, security, and scalability.

Why SCIM

The goal of SCIM is to automate the identity provisioning process, therefore, to reduce the cost of identity management and improve security. The automation process will simplify the user experience. SCIM is all about identity provisioning. So what is identity provisioning? Identity provisioning is creating, maintaining, and deleting user accounts and related identities in one or more systems or applications in response to business processes.

Let’s say that the company ABC uses some cloud applications like Gmail, Salesforce, and some other cloud applications. A new employee Bob joins the company. During the on-boarding Bob process, the HR manager wants to create a new user profile for Bob in the central identity directory and grant access to other services. It is not efficient for admins to enter user information in all those environments. At this point, the provisioning framework comes into the picture. The provisioning framework will tackle the burden of the admins. It will automatically provision the new users to those cloud applications and services.

Traditional way of provisioning

As you can see in the diagram, in the traditional mode of provisioning, each of the services will have its own way of communicating with the provisioning framework resulting in multiple connectors. This is a redundant integration effort for ECS and CSP. Maintaining and supporting these individual connectors will become a nightmare to admins and incur an extra cost. SCIM for identity provisioning was designed to mitigate such scenarios so that everyone agrees on an open protocol or a common way of communicating.

How Does SCIM Work?

The underlying concept of SCIM 2.0 is based on a common user schema, group schema, and an extension model that are exchanged via an HTTP based protocol. It has an object model where a Resource is the common denominator and all the other SCIM objects are derived from it. A resource must have an id, externalId, and meta as attributes. User, Group, and EnterpriseUser extend the common attributes. SCIM is not exclusive to these resources and may be extended to support other resource types.

Object model of SCIM

A SCIM server provides a set of resources, the contents that are allowed are defined by a set of schema URIs and a resource type. A “Resource” is a JSON object containing a “schema” attribute that indicates a list of one or more URIs included in the SCIM schemas. SCIM’s support of schema is attribute-based, where each attribute may have a different type, mutability, cardinality, or returnability. Validation of documents and messages is always performed by an intended receiver, as specified by the SCIM specifications. An attribute at least consists of the attribute name and one simple or complex value, either of which may be multi-valued.

Example for User resource

{
  "schemas": ["urn:ietf:params:scim:schemas:core:2.0:User"],
  "id": "2819c223-7f76-453a-919d-413861904646",
  "externalId": "701984",
  "meta": {
    "resourceType": "User",
    "created": "2010-01-23T04:56:22Z",
    "lastModified": "2011-05-13T04:42:34Z",
    "version": "W\/\"a330bc54f0671c9\"",
    "location": "https://example.com/v2/Users/2819c223..."
  },
  "userName": "[email protected]",
  "name": {
    "familyName": "Jensen",
    "givenName": "Barbara",
    "honorificPrefix": "Ms."
  },
  "displayName": "Babs Jensen",
  "profileUrl": "https://login.example.com/bjensen",
  "emails": [
    {
      "value": "[email protected]",
      "type": "work",
      "primary": true
    },
    {
      "value": "[email protected]",
      "type": "home"
    }
  ],
  "groups": [
    {
      "value": "e9e30dba-f08f-4109-8486-d5c6a331660a",
      "$ref": "https://example.com/v2/Groups/e9e30dba...",
      "display": "Tour Guides"
    }
  ]
}

SCIM Operations

SCIM provides a REST API with a rich but simple set of operations for resource manipulation.

SCIM Endpoints

The SCIM specifies well known endpoints for managing resources with the above operations. SCIM provides three endpoints; /Serviceproviderconfig, /Resourcetype, and /Schema to discover supported features and specific attribute details.