How user selection and custom account attribute filters work in User Access Reviews in RSA Identity Governance and Lifecycle
Originally Published: 2018-01-10
Article Number
Applies To
RSA Version/Condition: All
Issue
The filter does not seem to work correctly for all users.
In the example below you can see the review result is including one user whose Account Status=LOCKED. Ideally, the user should not have been included in the review result.
Resolution
As shown below the user molly is included in the review because she has an account in another business source whose status is not LOCKED.
One option here is to use an advanced expression to select the users to include that matches the business source(s) used in the access step:
users.id in accounts (accounts."Account Status"<>'LOCKED' and accounts."Application Name"='DAMS') .
After using the advanced filter you can see the account is excluded from review result.
Notes
Related Articles
The workpoint log has daily occurrences of ORA-02049: timeout: distributed transaction waiting for lock errors in RSA Id… 320Number of Views How users are selected for reviews that are triggered by rules in RSA Identity Governance & Lifecycle 25Number of Views How business source filtering works in an account access and ownership review in RSA Identity Governance & Lifecycle 46Number of Views RSA Governance & Lifecycle Recipes: Telemetry Chart - Daily Request Processing Summary 9Number of Views RSA Governance & Lifecycle Recipes: Overview - Daily User Changes 14Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?