Updating the Violation Manager attribute for a large number of RSA Identity Governance and Lifecycle applications
Originally Published: 2016-10-17
Article Number
Applies To
RSA Version/Condition: All
Issue
Resolution
- Perform an export of the application(s) where you desire to change the Violation Manager, it will create an .xml file.
- Before editing the exported .xml be sure to save a copy so you can revert to the original and be very careful when editing the file, as it is very sensitive to errors in the syntax.
- Open the .xml file in a text editor and note the highlighted sections:
- Edit the exported xml file and change the value of "<exceptionManagerID__Name>USERID</exceptionManagerID__Name>" to reflect the desired USERID and save the file.
- Import the updated .xml file into the environment.
Related Articles
Updating the certificate for a jks store and verifying the contents using keytool 115Number of Views When removing a user from a large number of Roles, the Change Request creation fails with an 'ORA-01704: string literal to… 81Number of Views Adaptiveauthentication- Db2 deadlocks can stop responding due to large number of records sin RSASESSION RSATRANSACTIOn an… 49Number of Views How to increase the max-pool-size for the Workpoint data source (WPDS) in RSA Identity Governance & Lifecycle 453Number of Views A large number of user sessions showing on the UI in SecurID Governance & Lifecycle 180Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Governance & Lifecycle 8.0.0 Administrators Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?