When creating a change request to remove access from a single user, the use of the Back and Next buttons allows two users to be selected in RSA Identity Governance & Lifecycle
Originally Published: 2020-04-03
Last Modified: 2023-10-06
Article Number
Applies To
RSA Version/Condition: 7.0.2, 7.1.0, 7.1.1, 7.2.0
Issue
This is best illustrated with an example. In the example below a request to remove access is initially created for user Cherry Blossom and through the use of the Back button the user is changed to Perry Scope. The end result is that both users are selected when only one user should be selected.
In the user interface go to Users > Users > Create Request button and select a user.
Click the Next button followed by the Back button. Change the user to Perry Scope.
Click the Next button followed by the Back button. Note both users are selected. The expected behavior is that only one user (Perry Scope) would be selected. Note the total at the bottom says 1 selected when there are 2.
Cause
Resolution
- RSA Identity Governance & Lifecycle 7.1.1 P07
- RSA Identity Governance & Lifecycle 7.2.0 P02
Related Articles
How to remove entitlements of a decommissioned application from user access in RSA Via Lifecycle and Governance 74Number of Views Remove Users from User Groups 19Number of Views In RSA Identity Governance & Lifecycle, duplicate entries are created when a user switches between two Identity Data Colle… 71Number of Views How user selection and custom account attribute filters work in User Access Reviews in RSA Identity Governance and Lifecycle 65Number of Views updateReviewItems web service fails to update review items when the UserID is the same for two users in RSA Identity Gover… 31Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme AFX Server and Remote Collection Agents fail to start after updating Java to version 1.8u241 (1.8.0_241) / 1.7u251 (1.7.0_… Upgrade Internal Authentication Manager Certificates to SHA-256 RSA Authentication Manager 8.9 Setup and Configuration Guide Upgrading the Internal SecurID Authentication Manager 8.6 Certificates to SHA-256
Don't see what you're looking for?