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
Running a form incorrectly filters on raw name when filtering on the Application Name attribute in RSA Identity Governance… 36Number of Views The display sequence of custom User Attribute Separators is incorrectly and unpredictably modified after making edits to U… 42Number of Views RSA Governance & Lifecycle Recipes: Report - Review Results - Review Summary Info 31Number of Views Data Access Collector (DAC) rejects Account Relationships when collecting Account Permissions in RSA Identity Governance &… 149Number of Views Report filter does not take changes in RSA Identity Governance and Lifecycle 15Number of Views
Trending Articles
RSA Release Notes for RSA Authentication Manager 8.8 Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA Authentication Manager 8.9 Release Notes (January 2026) How to create and configure certificates for HTTPS access when using intermediate CA certs in RSA Identity Governance & Li… Authentication Manager Supported Hardware and Upgrade Paths
Don't see what you're looking for?