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
Termination rule sometimes fails to create change requests to disable accounts in specific applications in RSA Identity Go… Number of Views Provisioning/Termination Rule does not create change requests to revoke entitlements if the rule also disables and/or dele… Number of Views Change Requests missing information in SecurID Governance & Lifecycle Number of Views The Edit and Cancel buttons in a Change Request cannot be disabled for requests created through Roles in RSA Identity Gove… Number of Views Partial failure in creating change requests with Java NPE error in RSA Governance & Lifecycle Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA SecurID Software Token 5.0.3 for Microsoft Windows Release Notes How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide
Don't see what you're looking for?
