Integrations
IDaaS allows you to create a Provisioner to provision users from IDaaS to a third-party service that supports System Cross Domain Identity Management (SCIM). When configured, IDaaS provisions users as they are added, modified, or removed from IDaaS to the third-party service. The provisioning process includes using groups and user attributes to identify the users that need to be provisioned. IDaaS integration templates include the mandatory user attributes needed for user provisioning, but custom attributes can also be included as part of the provisioning process.
This section describes how to configure user provisioning for available integration templates. To integrate a custom service for user provisioning, see the section, Manage provisioners using SCIM in the IDaaS Administration Online Help.
To use the Provisioners feature, you need a tenant with the premium or a consumer bundle.
After you add a provisioner, changing a group or attribute mapping triggers a large number of SCIM calls. Entrust recommends disabling the provisioner until you have completed all the required changes. When disabled, the only SCIM calls made are to delete users or provisioners, as applicable. In addition, you may need to reauthorize the provisioner if an authentication configuration has changed.
Topics in this section
AWS
This procedure describes how to integrate Amazon Web Services (AWS) for user provisioning.
GitHub
This procedure describes how to integrate GitHub for user provisioning.
Microsoft Entra ID (Inbound)
This integration allows Microsoft Entra ID (formerly Azure AD) to provision users and groups to IDaaS using SCIM 2.0. This is an inbound provisioning scenario where IDaaS acts as the SCIM server receiving user data from Entra.
Salesforce
This procedure describes how to integrate Salesforce for user provisioning.