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
RSA Governance & Lifecycle Federated Salesforce Connector Datasheet 23Number of Views RSA Governance & Lifecycle Integration: Workday Summary 27Number of Views RSA Governance & Lifecycle LotusNotes Connector Datasheet 14Number of Views RSA Governance & Lifecycle Oracle EBS Connector Datasheet 11Number of Views RSA Identity Governance and Lifecycle - IBM Notes Collector Datasheet 11Number of Views
Trending Articles
RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to Upgrade Internal SHA-1 Certificates to SHA-256 in Authentication Manager Using rsautil RSA Authentication Manager 8.9 Setup and Configuration Guide RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows
Don't see what you're looking for?