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
How to collect data from an RSA Authentication Agent 7.x for Windows for troubleshooting 245Number of Views Intermittent authentication issue with RSA Authentication Agent 7.4.3 for Windows 55Number of Views A more concise guide to updating Authentication Manager 8.x passwords 345Number of Views Microsoft Sentinel - High-Risk User API Integration Using Logic Apps and RSA OAuth Client - RSA Ready Implementation Guide 76Number of Views Cannot login with AveksaAdmin password after importing a database from another environment into RSA Identity Governance an… 215Number of Views
Trending Articles
Authentication Manager Log Messages (23001-23091) RSA Authentication Manager Upgrade Process How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?