capabilities.work

Provision and deactivate a Vyond user over SCIM 2.0

A 5-step recipe with Vyond. We can help you get access.

Recipe · 5 steps

Provision and deactivate a Vyond user over SCIM 2.0

with Vyond · Tenant Identity Federation

Enterprise user lifecycle against the RFC 7643/7644 SCIM surface.

  1. Read the supported schemas rather than assuming the attribute set.
  2. Check for an existing user before creating, so a 409 uniqueness conflict is avoided rather than handled.
  3. Create the user. A 403 here has three distinct causes — SSO not enabled, unsupported country, or insufficient team seats — distinguished only by reason. A 409 with scimType uniqueness means the email is already registered.
  4. Confirm the created user.
  5. Deprovision. There is no SCIM DELETE operation in the Vyond contract, so deactivation is a PATCH replacing active with false.
What you'll need to have ready
  • email: Becomes both userName and the primary email — Vyond requires them to match.
  • givenName
  • familyName
For your developer

Arazzo workflow vyond:scim-provision-user, 5 operations: ScimController.getSchemas → ScimController.getUsers → ScimController.createUser → ScimController.getUser → ScimController.patchUser. Specs on APIs.io.

More recipes with Vyond

Generate a Vyond video and export itTurbo text-to-video with a webhook subscription