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
Intercom-SecurID-Access-SAML-Integration 2Number of Views Terminated Users not correctly removed from Roles in RSA Identity Governance & Lifecycle 115Number of Views How to configure CP-Gaia-SuperUser-Access attribute to be returned 34Number 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 Some aliases are lost in a migration from Authentication Manager 6.1 to Authentication Manager 8.1 for users where there a… 26Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide User Application Portal The RSA Identity Governance & Lifecycle AD Collector and AD ADC authentication source fail to establish a TLS 1.2 SSL conn… RSA Authentication Manager 8.1 Quick Setup Fails with "Failed to Attach Replica Instance" How to Replace the Web Server Certificate for the RSA Identity Governance & Lifecycle Web Console
Don't see what you're looking for?