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 the Edit Users button from Account Review Results in RSA Identity Governance & Lifecycle 61Number of Views WebService createChangeRequest command "Remove account to group" does not populate the user information in request tab in … 37Number of Views How To Remove RSA-Addin from Outlook 2Number of Views How to define a Request Button in RSA Identity Governance & Lifecycle to allow single or multiple user selection based on … 29Number of Views How to remove entitlements of a decommissioned application from user access in RSA Via Lifecycle and Governance 74Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Unable to login to RSA Authentication Manager Security Console as super admin RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Governance & Lifecycle 8.0.0 Installation Guide Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6
Don't see what you're looking for?