How users and groups are synchronized from Cloud Pak for Data to OpenPages
In IBM® OpenPages® for IBM Cloud Pak for Data, you create and configure users and groups in Cloud Pak for Data and then they are synchronized to OpenPages.
- All of the users and groups that are created in Cloud Pak for Data are created under the CloudPak_Members group in OpenPages. Users are created with the default locale as it was configured for the user and group synchronization job.
- All users are created with default profiles as configured by the synchronization job unless the user is already assigned to a group associated with other profiles. You can assign profiles to a group in OpenPages using settings.
- Roles of users and groups that are created in Cloud Pak for Data are not transferred to OpenPages.
OpenPages administrators are able to change locale, profiles, and roles directly from within OpenPages. These settings take precedence over settings in Cloud Pak for Data and will not be overridden when a synchronization job runs.
For example, an OpenPages administrator can assign a profile to a user based on its group affiliation as a key (profile name) and comma-separated values (group name) in settings folder.
Properties that are overwritten in OpenPages by the user synchronization job
Because users and groups are synchronized from Cloud Pak for Data, if you change the following properties in OpenPages, your changes are overwritten when the synchronization job runs.
User properties
- User Name
- First Name
- Last Name
- Description
- All fields in Password and Security
Group properties
- Description
Adding and changing users and groups
The following table shows what happens when you create and modify users and groups.Action | Outcome |
---|---|
Create a group in Cloud Pak for Data and assign that group to the OpenPages instance. You can add existing users to the new group. | In OpenPages, if the group has users, it is created with name and description as specified in Cloud Pak for Data. The group is a subgroup under the CloudPak_Members group and existing users that are added to the group in Cloud Pak for Data are associated with the group in OpenPages. |
Create a user in Cloud Pak for Data. | In OpenPages, the user is a member of
the CloudPak_Members group by default.
Note: New users are not assigned a Role Template. The OpenPages administrator assigns Role
Templates.
|
Change the name of a group in Cloud Pak for Data. | A new group is created in OpenPages with the new name in the CloudPak_Members group. The group with the old name is moved into the Standalone Users and Groups group. Users are disassociated from the group in Standalone Users and Groups and associated with new group. |
Change the description of a group in Cloud Pak for Data. | The description of the group changes in OpenPages. |
Change the groups that a user is associated with in Cloud Pak for Data. | The group associations in OpenPages change to match that in Cloud Pak for Data. |
Delete a group in Cloud Pak for Data. | In OpenPages, the group is moved from the CloudPak_Members group to the Standalone Users and Groups in OpenPages. Users associated with that group that are members of other groups are no longer associated with the deleted group. The status of users who are not associated with other groups is changed to Inactive. |
Delete a user in Cloud Pak for Data. | The status of the corresponding user in OpenPages is set to Inactive. |
Remove a user from the list of users that can access the OpenPages instance in Cloud Pak for Data. | The status of the corresponding user in OpenPages is set to Inactive. For more information about removing a user from the list of users that can access the OpenPages instance, see Managing access to OpenPages instances. |
In Cloud Pak for Data, re-create a user that was previously deleted. | The status of the corresponding user in OpenPages is set to Active. |
Re-create a group in Cloud Pak for Data that was previously deleted. | In OpenPages, the group that was deleted moves from the Standalone Users and Groups group to the CloudPak_Members group. If any users exist in this new group, they are associated with the re-created group. |