Termination rule not generating a change request to disable the manually mapped accounts in RSA Identity Governance & Lifecycle
Originally Published: 2018-03-08
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 127Number of Views Termination rule sometimes fails to create change requests to disable accounts in specific applications in RSA Identity Go… 132Number of Views RSA Identity Governance and Lifecycle Provisioning -Termination rule is not generating change requests to revoke entitlements 81Number of Views Provisioning/Termination Rule does not create change requests to revoke entitlements if the rule also disables and/or dele… 172Number of Views Correct Termination Rule behavior in RSA Identity Governance and Lifecycle 7.x 124Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?