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
Can the application be upgraded when there are active Reviews in RSA Identity Governance & Lifecycle? 9Number of Views A single user has large spacing in the Users display in RSA Identity Governance & Lifecycle 31Number of Views RSA Governance & Lifecycle Google Apps Application Guide 14Number of Views Account Data Collectors (ADC) fail with ORA-00904: "RESOURCE_NAME": invalid identifier after upgrading RSA Identity Govern… 204Number of Views When removing a user from a large number of Roles, the Change Request creation fails with an 'ORA-01704: string literal to… 82Number of Views
Trending Articles
Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA Release Notes: Cloud Access Service and Authenticators RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device
Don't see what you're looking for?