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
How to configure WebSentry for different certificate access 19Number of Views How to query a public database schema table for Segregation of Duties (SOD) violations in RSA Identity Governance & Lifecycle 98Number of Views Publishing certificates with multiple OU values 12Number of Views 'Direct Members Missing' column under Role Entitlements tab incorrectly shows deleted, terminated and/or Role Members no l… 88Number of Views How to delete the RSA Authentication Manager 8.x virtual host Certificate Signing Requests (CSR) which show Pending/Inactive 1.4KNumber of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?