Admin guide to Version Management of Role Definitions with Role Revert Capabilities
This document provides detailed instructions on how administrators can manage role definitions and maintain a version history in Cymmetri Identity Governance and Administration (IGA). The solution supports full versioning of roles and allows roles to be reverted to previous states while maintaining control over target system configurations. When a role is rolled back, the system also ensures that the rollback applies to all target systems where the role has been assigned or deployed.
Role Versioning: All modifications to roles are tracked and stored as separate versions.
Target System Rollback: When a role is rolled back, the target systems where the role has been assigned will also revert to the previous configuration.
Audit Trail: Administrators can view the complete history of changes made to any role.
Rollback Functionality: Ability to revert a role and its assignments to any previous version.
Controlled Access: Only authorized administrators can manage role versions and apply rollbacks.
Administrator-level access to Cymmetri IGA.
Ensure roles and permissions are configured to allow role version management and rollback capabilities.
Target systems should be integrated with Cymmetri IGA and configured for automatic updates when roles are reverted.
Login to Cymmetri IGA using your administrator credentials.
Navigate to Identity Governance.
Click on Role Management.
In the Role Management module, search for the specific role whose version history you want to view.
Select the role from the list.
On the role details page, click on the History/Versioning tab.
A list of all previous versions will be displayed, along with the following information:
Version Number
Date of Modification
Modified by (Administrator’s name)
Description of changes made
To compare two versions of a role:
In the History/Versioning tab, select the two versions you want to compare by checking the boxes next to them.
Click the Compare button.
A side-by-side comparison will be displayed showing the differences in permissions, attributes, and other relevant configurations.
In the Role Management module, select the role you want to roll back.
Go to the History/Versioning tab and locate the version to which you want to revert.
Click the Rollback button next to the desired version.
A confirmation dialog will appear, detailing the rollback process. Confirm your action by clicking Yes.
Role Revert on Target Systems: When rolling back a role, Cymmetri IGA will automatically push the changes to the target systems where this role has been deployed, ensuring the role reversion is applied across all systems where the role is in use.
The role will now be reverted to the selected version, and a new version will be created documenting the rollback action. The target systems will reflect the same version.
The system will generate a notification once the rollback is complete and applied to all integrated target systems.
To view a complete audit log of all role modifications and reverts:
Navigate to the Audit Reports section from the dashboard.
Select Role Change History or Target System Rollback Logs.
Filter the report based on role name, date, or administrator.
The report can be exported in PDF or Excel format for compliance purposes.
Only authorized administrators can manage and roll back role versions and apply the changes to target systems. To assign or revoke this permission:
Navigate to Configurations → Admins.
Select the Domain Admin role or click on Add button to search for a user to assign the Domain Admin role.
When a role version is rolled back and applied to target systems, Cymmetri IGA will trigger notifications to relevant stakeholders and system owners:
Navigate to Notification Settings under Configurations.
Enable the Role Version Rollback and Target System Revert Notification and configure the recipient list.
Customize the email template if required.
Real-Time Monitoring: Use the Monitoring Dashboard to track the status of role rollbacks and ensure that all target systems have received the updated configurations.
Regular Audits: Conduct regular audits of role definitions and their versions to ensure compliance and avoid unauthorized changes.
Testing Before Rollback: Before rolling back a critical role in a production environment, it’s advisable to test the rollback in a staging environment.
Confirm Target System Updates: After a rollback, verify that all target systems reflect the correct version of the role.
Unable to Roll Back: Ensure that you have the required permissions to perform a rollback and that the selected version is valid.
Target Systems Not Updated: If the role reversion has not propagated to the target systems, check the integration settings for those systems and confirm that the connection with Cymmetri IGA is active.
Audit Log Not Displaying Changes: If the audit log doesn’t display recent changes, verify that role versioning is enabled in system settings.
Cymmetri IGA's version management feature allows for seamless role reversion, ensuring that not only are previous versions of roles maintained, but any rollbacks are also applied across all target systems. By following this admin manual, administrators can effectively manage role versions and ensure compliance, security, and consistency across their identity governance landscape.