How user selection and custom account attribute filters work in User Access Reviews in RSA Identity Governance and Lifecycle
Originally Published: 2018-01-10
Last Modified: 2023-10-06
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
Error encountered in Relying Party servlet: (404)Not Found' appears in web browser when using RSA Federated Identity Manag… 21Number of Views DBSM - Unable to remove the last user from a role 1Number of Views Cancel User Requests 87Number of Views How to suppress the warning message that Change Requests have not been generated when completing a Review in RSA Identity … 22Number of Views How to remove unnecessary tables from database statistics analysis in RSA Identity Governance & Lifecycle 97Number of Views
Trending Articles
Don't see what you're looking for?