The Idaptive Developer Program

Thank you for your interest in the Idaptive Developer Program!

We are currently busy writing kickass API documentation so you can focus on building amazing apps and leave authentication to us. In the meantime, please note that some of the references mention Centrify, as our code base is similar.

Cheers,
Idaptive Team

SCIM Provisioning Overview - Client

Describes Idaptive's outbound SCIM provisioning implementation (SCIM client)

SCIM Overview

SCIM (System for Cross-domain Identity Management) is an open standard for automating the exchange of user identity information between identity domains, or IT systems.

Use SCIM to automatically provision and de-provision user accounts in external systems such as SAML apps. For more information about SCIM, see www.simplecloud.info.

Outbound provisioning provisions users and groups from Idaptive to other applications.

Idaptive's Outbound SCIM Provisioning

Idaptive supports provisioning to some applications through their proprietary API. For example, provisioning to Office 365 is done using API from Microsoft. Other apps (e.g., custom SAML apps) can only be provisioned if the app supports SCIM.

A SCIM server is only required for outbound provisioning, so users and groups can be provisioned from Idaptive to your application. Idaptive's outbound provisioning feature supports SCIM 1.1 and 2.0.

If your SAML application supports SCIM, you can enable provisioning by entering the Access Token and SCIM URL.

Idaptive Provisioning Requirements

Before configuring your application for provisioning, you must:

  • Install, configure, and deploy the app
  • Give Manage Accounts and Manage Groups permissions to the app
  • Get an Access Token for the app

Note

When you create the app, the Access Token is only displayed once and it never expires. It is important to store the Access Token in a secure location.

More Info

SCIM Provisioning Overview - Client


Describes Idaptive's outbound SCIM provisioning implementation (SCIM client)

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.