Sign in
Catalog / Hands-on lab

Lab: SCIM provisioning and webhooks

Push accounts from your own lab tenant to a real SCIM 2.0 target: create the application and its key, send a pilot group, remove a user and watch the account go, schedule a sync and deliver a webhook.

Monosign University Pass 1 hAdvanced DE · EN · ES · TR Developer

Version 4 · updated Nov 9, 2026What changed?

Hands-on lab
Sign in to start

Included with University Pass.

What you will learn

  • Call the Monosign API with an application key that holds only the permission it needs
  • Push users and a group to a SCIM target and confirm what arrived
  • Explain how removing an assignment deprovisions the account on the target
  • Schedule auto-sync and read a webhook's delivery state

Your lab environment

YOUR LAB SERVERYour browserManagement and theweb terminalManagementscim-demo, its key,SCIM settings,webhooksMonosignservicesSCIM sync,auto-sync, webhookdeliverySCIM targetSCIM 2.0 atlab-apps, receivespush and DELETEWeb terminalcurl to the API andto lab-appsMonosign APIREST key with onepermissionWebhookreceiverStores eachdelivery at lab-appsLab usersayla, berk, cem in scim-pilot; deniz, egeAssigns aylaLogin Success
Your lab environment: Monosign pushes assigned users and the pilot group to the lab SCIM target and delivers a webhook to the lab receiver

Lab tasks

Each task is checked automatically against the real state of your lab environment.

  1. 1. Create the application scim-demo with a REST API key, then use the key to assign ayla
  2. 2. Turn on SCIM for scim-demo and push ayla to the target with Force Sync
  3. 3. Push the scim-pilot group with its three members, and nobody else
  4. 4. Remove cem from scim-demo and confirm the target deleted the account
  5. 5. Schedule auto-sync and let one scheduled run happen
  6. 6. Define a webhook to the lab receiver, send one delivery and read its state