About Provisioning
Provisioning refers to action of using Registry data to create or remove access to applications and services. COmanage Registry defines a mechanism to extract Registry data for provisioning (via plugins), but there are multiple ways to provision applications from Registry:
- Push Provisioning: Using Registry plugins, Registry notifies applications when relevant data has changed.
- Pull Provisioning: Applications pull data from Registry on demand, either via the REST API or (less desirably) via database views.
- Messaging: Upon change of relevant data, a message is issued to a Message Queue or Enterprise Service Bus, which is then responsible for distributing the message to the relevant downstream applications.
Push Provisioning
In order to enable Push Provisioning, one or more Provisioning Plugins must be installed. By default, Registry ships with the following Plugins:
Plugin |
Description |
Notes |
|---|---|---|
Exports transactions as JSON to a changelog file |
Disabled by default |
|
Provisions data to an LDAP server |
|
You can also write a custom plugin.
Adding a Provisioning Target
The first step to setting up provisioning is defining a Provisioning Target. Login as a CO Administrator and go to Organizations > YourCO > Configuration > Provisioning Targets.
Pull Provisioning
Generally, pull provisioning from Registry is not recommended, as it ties applications tightly to the Registry implementation. Use of an intermediary such as LDAP is recommended.
(via LDAP)
Messaging
This model is not currently supported (CO-583).