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
High CPU utilization caused by Webservice calls embedded in request forms in RSA Governance & Lifecycle Number of Views 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 Access policy is not enforced for some users in RSA Cloud Authentication Service Number of Views Database backups from the user interface gets stuck 'In Progress', never finish, and prevent future backups in RSA Identit… Number of Views
Trending Articles
How to recover the Application and AFX after an unexpected database failure in RSA Identity Governance & Lifecycle Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager Upgrade Process
Don't see what you're looking for?
