Segregation of Duties rule returns unwanted violations if the same entitlement definition exists in both entitlement sets in RSA Identity Governance & Lifecycle
Originally Published: 2020-02-12
Article Number
Applies To
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x
Issue
For example, in the SOD rule definition below, the intent is to find any user with two or more Aveksa entitlements. However, processing this rule returns users with single Aveksa entitlements as well.
Cause
Resolution
Workaround
Related Articles
After refreshing a user access review, the business source values for roles (role sets) display as null in RSA Identity Go… 30Number of Views FileNotFoundException while creating an entitlement collector in RSA Identity Governance and Lifecycle 40Number of Views What is the meaning of yellow flags in Microsoft Internet Explorer's icons for critical extensions? 7Number of Views Generic REST EDC collector not getting the desired results in entitlement relationship in RSA Governance & Lifecycle 49Number of Views How to query a public database schema table for Segregation of Duties (SOD) violations in RSA Identity Governance & Lifecycle 99Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) Clarification on RSA Identity Router (IDR) Upgrade Notification (12.22.0.0.37) Troubleshooting AFX Server issues in RSA Identity Governance & Lifecycle Downloading RSA Authentication Manager license files or RSA Software token seed records RSA Release Notes for RSA Authentication Manager 8.8
Don't see what you're looking for?