...
Provisioning of groups from Registry into Grouper is per CO with all groups for a CO provisioned under a single (configurable) stem or folder in Grouper. All groups in Registry, with the exception of the 'admin' and 'members' groups for COUs, are provisioned directly under the configured stem or folder for the CO. The 'admin' and 'members' groups for COUs are provisioned into a stem or folder hierarchy that mirrors the COU parent-child relationship (if any) in Registry.
| Note |
|---|
How the Grouper Provisioner chooses and provisions the identifier for Grouper to use for the subject (ie. the user or member) has changed as of version 1.1.0 of COmanage Registry. A legacy mode configuration is available for deployments that wish to upgrade to version 1.1.0 without changing the Grouper Provisioner configuration, but the legacy mode is deprecated and will be removed in a later release. Please see the documentation on configuration and consult with the COmanage developers if you have questions. |
| Note |
|---|
If you plan for users to access the Grouper UI and for that access to be managed using COmanage Registry, we recommend you create a CO unique identifier and use it as the expected identifier that the Grouper UI will see and map to subjects (Grouper users). |
...