Provisioning Termination rule is not generating change requests to disable accounts in RSA Identity Governance and Lifecycle
Originally Published: 2017-07-10
Last Modified: 2023-10-06
Article Number
Applies To
RSA Version/Condition: 7.0.1
Issue
For example,
- Create a Provisioning Termination Rule to disable accounts.
- Pick any user who has accounts under the User > Access tab.
- Now delete that user from the system.
- Process the rule and you will see that no change requests were generated to disable the accounts.
- The User's access tab shows that all the accounts are removed from that user.
Cause
Resolution
Related Articles
Termination rule sometimes fails to create change requests to disable accounts in specific applications in RSA Identity Go… 135Number of Views Termination rule not generating a change request to disable the manually mapped accounts in RSA Identity Governance & Life… 43Number of Views Disable an RSA Authentication Manager user account using the Administration API 50Number of Views How to configure the Enable, Disable, Lock, and Unlock actions in an Account Review in RSA Identity Governance & Lifecycle 96Number of Views Termination rule fails to detect a user when the user has multiple accounts in a group in RSA Governance & Lifecycle 66Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?