Empty Termination Change requests created for users that are deleted in RSA Governance & Lifecycle
Article Number
Applies To
RSA Version/Condition:
- RSA Governance & Lifecycle 7.5.2 P07
Issue
After the user is deleted, there is an empty change request opened for the user that was deleted in RSA Governance & Lifecycle.
Cause
In this case, only one change request should be created for both delete and revoke entitlement actions; however threads are created simultaneously, leading both functions to be treated as different entries in validateExistingCRItemsForSameRule().
This results in the creation of two duplicate change requests for the same item, but the empty change request lacks displayed deleted values.
Resolution
- RSA Governance & Lifecycle 8.0.0 P02
Related Articles
ACE/Server LDAP synchronization: Recovering users that were auto-deleted by filter Number of Views Error: 'Cannot activate this token. There is no outstanding request that matches the userID and activation code' Number of Views Offline logon failure then loop back to login screen RSA Authentication Agent 7.3.3 [99] for Windows Number of Views 'su -' doesn't prompt for passcode on SUSE with PAM Agent Number of Views OAuth 2.0-Based Permissions for the Cloud Administration APIs Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.8 Setup and Configuration Guide
Don't see what you're looking for?
