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
Request a Cloud Access Service Account 31Number of Views RSA Identity Governance and Lifecycle Provisioning -Termination rule is not generating change requests to revoke entitlements 81Number of Views Failure to map other accounts collected by MAADC, Only the first collected account is mapped in RSA Governance & Lifecycle 92Number of Views Request could not be handled error in RSA Identity Governance & Lifecycle Request Forms 100Number of Views This request contains no changes. It cannot be submitted error when adding entitlement belonging to a role in RSA Identity… 24Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA Authentication Manager Patch Updates How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Artifacts to gather in RSA Identity Governance & Lifecycle
Don't see what you're looking for?