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 Failure to map other accounts collected by MAADC, Only the first collected account is mapped in RSA Governance & Lifecycle 92Number of Views Attribute change rule creating duplicate change items for users having more than one account with same entitlement in an a… 33Number of Views Multi-app Entitlement Data Collector (MAEDC) fails with DuplicateNameException in RSA Identity Governance & Lifecycle 126Number of Views Unauthorized change rule triggered although change request for add access has passed approval phase in RSA Identity Govern… 50Number of Views
Trending Articles
RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to Upgrade Internal SHA-1 Certificates to SHA-256 in Authentication Manager Using rsautil RSA Authentication Manager 8.9 Setup and Configuration Guide RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows
Don't see what you're looking for?