Updating the Violation Manager attribute for a large number of RSA Identity Governance and Lifecycle applications
Originally Published: 2016-10-17
Last Modified: 2023-10-06
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
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 When adding User Attributes in RSA Identity Governance and Lifecycle 7.1.0 the following error appear: The number of param… 14Number of Views Delete a Large Number of Expired Tokens from the Authentication Manager 8.x Database 116Number of Views Adaptiveauthentication- Db2 deadlocks can stop responding due to large number of records sin RSASESSION RSATRANSACTIOn an… 49Number of Views A single user has large spacing in the Users display in RSA Identity Governance & Lifecycle 31Number of Views
Trending Articles
Artifacts to gather in RSA Identity Governance & Lifecycle How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle How to Download and Reinstall the AFX Server Archive in RSA Governance & Lifecycle
Don't see what you're looking for?