Migrating Closed User Groups migrating-closed-user-groups
Currently, Closed User Groups (CUG) need some additional steps to be functional in the destination environment of a migration. This document explains the scenario, and the steps required to have them protect nodes in the intended way.
Migration of Closed User Groups (CUGs)
Groups are automatically included in a CTT/CAM migration to Adobe Experience Manager as a Cloud Service if they are associated to the migrated content via that content’s ACL or its CUG policy node. Verifying that the group and its members exist should be done before going live. Groups referenced on a CUG policy are referred to here as “CUGs groups.”
To use CUGs in AEM as a Cloud Service, users must be present on the Author instance and be members of the relevant CUGs groups. This can be accomplished using packages, or if the CUGs users are IMS users, they may already be present. CUGs users must then be made members of the AEM CUGs groups.
To enable CUGs behavior on the Publish instance,
- The CUGs groups must be activated (which replicates them and their members to the Publish instance),
- All pages protected with CUGs policies must be unpublished (to clear the global CUGs count), and
- The pages protected with CUGs policies must then be published (which enables the Publish instance and to track the policies).
- After all the pages are published, verify the functionality for each CUG protected page.
For additional information, see Closed User Groups.