Provisioning is the action of exporting Registry data to downstream applications, generally for the purposes of creating or removing access to those applications. Registry provisioning is implemented by Provisioner Plugins.
Provisioning Targets are configured via Configuration > Provisioning Targets.
When a change is made to a Provisionable Object or a Secondary Object related to a Provisionable Object, Registry will immediately try to run the Provisioning Target. If provisioning fails, it will not automatically be retried.
The Provisioning Target is available, but provisioning will only happen when manually requested by an Administrator.
The Provisioning Target is not available.
Provisioning Targets may be ordered, in which case the Provisioning Target with the lowest order (eg: 1) will be run first. This is useful where downstream applications may have dependencies, such that one application must be provisioned first.
Select the desired Plugin from the available set.
Once set, the Plugin associated with the Provisioning Target cannot be changed. (AR-ProvisioningTarget-1) |
After the Provisioning Target is initially added, the Plugin Configuration will become available. Specifics of this configuration vary by Plugin, see the Plugin's documentation for more information.
Registry supports provisioning Objects as per this table:
Provisionable Object | Associated Objects Included | Eligibility Rules |
---|---|---|
COUs |
| |
Groups |
|
|
People |
1Only these associated objects are included for Deleted People |
|
Types |
|
As shorthand, the record constructed as described above for Ineligible objects is referred to as the "Core" record, and the record constructed for Eligible objects is referred to as the "Full" record.
Provisioning History Records are created for all provisioning events, for all types of Provisionable Objects.