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
Provisioning Termination rule is not generating change requests to disable accounts in RSA Identity Governance and Lifecycle 131Number of Views Duplicate Local Entitlements may occur when Provisioning Local Entitlements through Manual Activities in RSA Identity Gove… 28Number of Views Termination rule sometimes fails to create change requests to disable accounts in specific applications in RSA Identity Go… 135Number of Views Comments and History of Canceled Change Requests generated via Reviews show as Canceled by System instead of the User who … 32Number of Views Attribute Change Rule not generating Change Requests in SecurID Governance & Lifecycle 87Number of Views
Trending Articles
Artifacts to gather in RSA Identity Governance & Lifecycle How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle How to Download and Reinstall the AFX Server Archive in RSA Governance & Lifecycle
Don't see what you're looking for?