...
Plugin | Description | Notes | |
|---|---|---|---|
Exports transactions as JSON to a changelog file | Disabled by default | ||
| GitHub Provisioning Plugin | Provisions group (team) memberships to GitHub | ||
Provisions data to a MACE Grouper deployment | |||
Provisions Unix home directories | Experimental | ||
Provisions data to an LDAP server | |||
| Mailman Provisioning Plugin | Provisions email lists and subscriptions to Mailman | Experimental | |
| MediaWiki Provisioning Plugin | Provisions to MediaWiki | Experimental |
...
- Login as a CO Administrator and select your CO.
- Go to Configuration > Provisioning Targets.
- Click (+) Add Provisioning Target.
- Configure the new Provisioning Target.
- If the Plugin you select has additional configuration options (most do), they will appear after you click Add.
- Plugins configured for Automatic Mode will be invoked automatically whenever COmanage Registry notices data suitable for provisioning has changed. Plugins configured for Manual Mode will only be invoked when a CO Admin explicitly does so (as described below). As of Registry v3.2.0, Plugins can be configured in Enrollment Mode. Plugins in Enrollment Mode will only be invoked once, at the conclusion of an Enrollment Flow.
- As of Registry v1.0.3, Provisioning Targets can be ordered, so that a given provisioner can be guaranteed to run before another provisioner (for the same record). This applies only during Automatic Provisioning.
As of Registry v2.0.0, a Provisioning Group can be specified. If provided, only CO People who are members of the CO Group (and only the CO Group itself, if the Provisioning Target also supports provisioning groups) will be provisioned using this provisioner. If a CO Person is subsequently removed from the group, their record will be deleted from the target (that is, the provisioning operation will automatically be converted to a delete action).
Note Keep in mind that when a CO Person is not in Active or Grace Period status, they are effectively removed from all Groups (with the exception of All Members Groups) for purposes of provisioning. So, for example, if a CO Person is expired, and the Provisioning Target is configured for the I Like Ice Cream Group (of which the person is a member), they will be completely removed from the Provisioning Target. Only All Members groups (at either the CO or COU level) can be used to maintain an expired record in the Provisioning Target (assuming the Target supports such behavior in the first place).
As of Registry v3.2.0, an Organizational Identity Source can be associated with a Provisioning Target, via the Skip If Associated With Org Identity Source configuration option. If set, then a CO Person who has an Organizational Identity created from the specified Organizational identity Source will not be provisioned.
Note If used with a Provisioning Group, this setting takes precedence, and will prevent the CO Person from being provisioned.
- Configure any Plugin specific options.
...