{"id":3812,"date":"2021-11-05T05:03:00","date_gmt":"2021-11-05T05:03:00","guid":{"rendered":"https:\/\/www.adminbyrequest.com\/?p=3812"},"modified":"2026-01-25T07:57:03","modified_gmt":"2026-01-25T07:57:03","slug":"scim-integration","status":"publish","type":"post","link":"https:\/\/www.adminbyrequest.com\/en\/blogs\/scim-integration","title":{"rendered":"SCIM Integration"},"content":{"rendered":"\n

Chances are, your enterprise is already making the most of the reusable, normalized, open standard that is the<\/h2>\n\n\n\n

System for Cross-Domain Identity Management (a.k.a. \u2018SCIM\u2019).<\/h2>\n\n\n\n

Lightweight, simple, and growing in popularity \u2013 we\u2019ve now made it possible to integrate with Admin By Request.<\/h1>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n

Overview<\/h2>\n\n\n\n

If you\u2019re new to SCIM, the protocol was created to help manage user identity information. In simple terms, it does this by defining how an Identity Provider (IDP) and supported applications talk to each other.<\/p>\n\n\n\n

The SCIM protocol provides standard definitions for users and groups, i.e., a schema with a default set of values for what should be defined for users, and what should be defined for groups.<\/p>\n\n\n\n

With this, comes a set of standard operations and a RESTful API which translates these operations into GET<\/strong>, POST<\/strong>, PUT<\/strong>, PATCH <\/strong>and DELETE <\/strong>HTTP requests. These HTTP requests run the typical operations involved in user and group management, such as Create<\/strong>, Update<\/strong>, and Delete<\/strong>, with responses returned in JSON data format.<\/p>\n\n\n\n

Benefits of SCIM Integration<\/h2>\n\n\n\n

At one end you have your IDP environment \u2013 such as Azure AD or Okta \u2013 used to create, maintain, and manage user information: the central hub for all things user-identity related.<\/p>\n\n\n\n

At the other end you have the many applications that you want your users to have easy and secure access to.<\/p>\n\n\n\n

In between, you have SCIM: the communication channel used to provision users by pushing the actions undertaken on the IDP side, to connected applications.<\/p>\n\n\n\n

The main goal being, to save IT admins from having to onboard and manage user identities and user access manually on multiple different applications. With SCIM, you can do it all from the IDP side, with changes automatically reflected on integrated applications when the provisioning cycle runs.<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

What Our Integration Offers<\/h2>\n\n\n\n