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 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 Segregation of Duties (SOD) Rule fails with error 'ORA-30926: unable to get a stable set of rows in the source tables' err… 231Number of Views Authentication Manager 8.1 SP1 conflict between NTP time and VMWare Host time, both set 111Number of Views Access Requests and Workflows rely on the Application Server and Database Server times to be in synch in RSA Identity Gove… 29Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?