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
Intercom-SecurID-Access-SAML-Integration 2Number 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 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 Authentication Manager 8.1 SP1 conflict between NTP time and VMWare Host time, both set 110Number of Views RSA Identity Governance & Lifecycle Role Collector (RDC) fails with ORA-30926 error 121Number of Views
Trending Articles
How to delete old or pending certificate signing requests for RSA Authentication Manager console or virtual host replaceme… Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to import CA signed console cert from AM 8.x primary into a new primary with same FQDN How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings.
Don't see what you're looking for?