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
Last Modified: 2023-12-01
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
If the RSA Identity Governance and Lifecycle Rule Status is invalid, a Segregation of Duties (SOD) rule definition takes … 51Number of Views BlackBerry browser get stuck on javascript collector 19Number of Views Segregation of Duties (SOD) Rule fails with error 'ORA-30926: unable to get a stable set of rows in the source tables' err… 232Number of Views "The request could not be handled" message occurs in the RSA Identity Governance & Lifecycle UI when a rule remediator is … 66Number of Views Slow INSERT statement executing from the SoD_Rule_Pkg in RSA Identity Governance & Lifecycle 115Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?