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
Failure to map other accounts collected by MAADC, Only the first collected account is mapped in RSA Governance & Lifecycle 94Number of Views Manually unmapped accounts are not rejected in the collection and remain as an Orphan accounts in RSA Governance & Lifecycle 73Number of Views Another Mapping already exists for the target account attribute warning in RSA Identity Governance & Lifecycle when settin… 69Number 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 How to resolve the issue of logging proxy server IP address for every request 10Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA-2026-10: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities RSA SecurID Desktop Token 5.0.3 for Windows Administrator's Guide RSA SecurID Software Token 4.2.1 for Mac OS X Administrator's Guide Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update
Don't see what you're looking for?