...
- All parts of provisioning configuration are performed in the Grouper UI with helpful documentation, wizard-like interfaces, descriptive validations, and diagnostic tests.
- All provisioners have consistent configuration concepts and terms so adding the next provisioner will be easy.
- Configuring new provisioners or editing existing provisioners do not require Grouper to be redeployed/restarted.
- Provisioning configuration starts with an “external system”, which is the connection information to connect to the target to provisioning to.
- External systems can be re-used among provisioners, or for other parts of Grouper (e.g. loader, “custom UI”). The provisioner itself is configured next.
- Scaffolding (start with) can help you get started with provisioning configuration.
- There are the daemon jobs for the full or incremental sync which are scheduled.
- All provisioners have a standard object model. Translating data from Grouper to the target format is consistent across all provisioners.
- You configure which data from Grouper gets sent to the target and how it is formatted
- There are provisioning-specific screens to identify which objects (groups, users, memberships, attributes) are sent to the target.
- Provisioner specific metadata can be assigned to Grouper objects to inform provisioning actions.
- When the provisioner is up and running, data propagation is verified and errors info is readily available
...
- The DAO is how Java talks to the target. This would implement CRUD operations and hopefully do so in bulk
- "Target beans" can be subclassed if needed
- The provisioner specifies the class names of all the mandatory and optional subclasses
- The logic is what takes the beans and decides what has changed and runs the actions to sync or notify or log
- The configuration class will translate from the properties file to java, and validate the configuration
- The translator will translate from Grouper objects to Target objects (and vise versa), based on configuration and potentially cache
- The Grouper DAO will get objects from Grouper efficiently based on which field is being retrieved
- The target classes can be subjclassed subclassed for Grouper
- The Subject DAO will get objects from the subject source
- The target objects for subjects can be subclassed
...
See this page
Provisioning to Azure
See this page
Provisioning to other systems
...