How to close Open Violations for inactive Segregation of Duties (SoD) and User Access Rules in RSA Identity Governance & Lifecycle
Originally Published: 2020-04-14
Article Number
Applies To
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x
Issue
- Open violations remain open after the rule has been inactivated.
- Exceptional access remains in effect and on the exceptional access expiration date, the violations become open violations and emails are sent to the remediators to take action.
Tasks
Resolution
- Delete the rule
- Change the rule:
- Edit the SoD or User Access rule.
- Set the status to Active
- Change the Selected users filter to something that is always false (for example, go to Advanced and enter 1=0 in the Where Clause).
- Save the rule changes.
- Run the rule once. This should close all violations.
- Edit the rule again
- Set the status to Inactive
- Remove the false filter.
- Save the rule changes.
Related Articles
RSA Identity Governance & Lifecycle requests stuck in an open state due to datafile resizing Number of Views User Access Rule is not generating the Change Request due to open violations. Number of Views How to track and monitor RSA Via Lifecycle & Governanace remediation action status for violations generated from Segregati… Number of Views Poor performance when processing SoD Rules that use a Correlation Attribute in RSA Identity Governance & Lifecycle Number of Views All change requests are stalled or in open state in RSA Identity Governance and Lifecycle Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Release Notes for RSA Authentication Manager 8.8 Deploying RSA Authenticator 6.2.2 for Windows Using DISM Downloading RSA Authentication Manager license files or RSA Software token seed records
Don't see what you're looking for?
