How to move the mapped AD security groups to a different OU without losing authentication access...
When you move one of the mapped AD security groups for authentication (e.g. CA-Admins, CA-Auditors, CA-SafeManagers, CA-EndUsers) to a different Active Directory OU, authentication will fail. The OU path for the mapped groups are "hard coded" for their path and need to be updated.
Steps
- Move one of the Active Directory authentication security groups to a different OU
- Log into the PVWA portal with your local CyberArk administrative account (e.g. Privilege Cloud it is your _admin account)
- Go to Policies --> Safes
- *** This is temporary *** Add the moved AD security group to any safe (this task will update the "hard coded" path on the backend with the new OU location)

- Log into the PVWA portal with a user account that is a member of the moved group
- *** Note *** The first login may not provide all the permissions as previous
- Logoff and log back into the PVWA to see all the permissions restored
- Once authentication/permissions are confirmed, log back into the PVWA via the CyberArk administrative account and undo the temporary permissions assigned in step #4
Note that a REST API call to Add Member to Safe, where the LDAP group is added, for example, to a newly created empty safe, also works to remap the group's DN and OU. See documentation:
https://docs.cyberark.com/Product-Doc/OnlineHelp/pas/Latest/en/Content/WebServices/Add%20Safe%20Member.htm?tocpath=Developer%7CREST%20APIs%7CSafes%7CSafe%20members%7C_____1