Docs/SCIM Provisioning/Overview

SCIM Overview

SCIM 2.0 (System for Cross-domain Identity Management) automates user and group provisioning between your identity provider and SecureCodingHub. Add, update, and remove users without manual intervention.

What is SCIM?

SCIM automatically syncs user lifecycle events from your identity provider to SecureCodingHub: create a user on hire, update attributes on change, and deactivate on offboarding. It eliminates manual user management entirely.

Supported Operations

SecureCodingHub's SCIM 2.0 endpoint supports the following resources and operations:

ResourceOperations
UsersCreate, Read, Update, Delete, List, Filter
GroupsCreate, Read, Update, Delete, List
Service Provider ConfigRead (discovery)
SchemasRead (discovery)
Resource TypesRead (discovery)

Authentication

The SCIM API uses Bearer token authentication. Generate a token from the SecureCodingHub admin panel and configure it in your identity provider.

SettingValue
Base URLhttps://api.securecodinghub.com/api/sch/scim/v2
Auth HeaderAuthorization: Bearer {your-scim-token}

How It Works

Setting up SCIM provisioning is a straightforward four-step process:

1

Admin generates a SCIM token in SecureCodingHub

2

Token is configured in the identity provider (Okta, Azure AD)

3

IdP pushes user/group changes to SecureCodingHub SCIM endpoint

4

Users and teams are created, updated, and removed automatically

Good to know: SCIM provisioning works alongside SSO. SSO handles authentication; SCIM handles user lifecycle management.