Termination rule not generating a change request to disable the manually mapped accounts in RSA Identity Governance & Lifecycle
Originally Published: 2018-03-08
Last Modified: 2023-11-30
Article Number
Applies To
RSA Version/Condition: 7.0.1, 7.0.2
Issue
Steps to Reproduce
- Manually map a user to an account which is not shared in an application which has Allow Account Disabling set to Yes.
- Create a rule with the following configuration:
- Delete the user from source.
- You will see that a change request is not created for the user:
Cause
Resolution
Related Articles
Attribute Change Rule not generating Change Requests in SecurID Governance & Lifecycle 87Number of Views Attribute change rule creating duplicate change items for users having more than one account with same entitlement in an a… 35Number of Views Provisioning Termination rule is not generating change requests to disable accounts in RSA Identity Governance and Lifecycle 130Number of Views The Cancel Pending Requests button on the Pending Submissions page is disabled in RSA Identity Governance & Lifecycle 67Number of Views How to stop RSA Via Lifecycle & Governance (IMG) review items from reverting back to the default state after a change requ… 104Number 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 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
Don't see what you're looking for?