RSA Identity Governance & Lifecycle 7.0.x provisioning termination rule is not creating a change request to disable the manually linked accounts
Originally Published: 2018-06-26
Article Number
Applies To
RSA Version/Condition: 7.0.1, 7.0.2
Issue
- Create a termination rule to generate change request to disable the accounts when the user is deleted.
- In this example, we have picked a user who has two accounts (one is a collected account and the other one is a manually linked account):
- Delete the user from the source and run the corresponding Identity data collector to collect the deleted user.
- Now run the rule and it will be able to pick the deleted user. The rule will create a change request to disable the collected account but doesn't create a change request to disable the manually linked account.
Cause
Resolution
NOTE: If you are seeing this issue for a specific application/directory or post upgrading to V7.0.2 P05+, please verify if the allow account disabling flag is set to Yes. If this is set to No,
- Navigate to Resources > Applications/Directories.
- Select the application/directory and click Edit.
- Enable the flag and click OK.
Related Articles
How to disable Ping Internet Control Message Protocol (ICMP) reply on RSA Authentication Manager 8.1 55Number of Views Configure a Web-Tier Self-Service Console Logon Banner on Windows 56Number of Views DSA-2019-129: RSA Identity Governance and Lifecycle Security Update for SUSE Linux Enterprise Server Vulnerabilities 11Number of Views Anti-virus agent best practices for enVision 67Number of Views Run a Report Job 20Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) How to install the jTDS JDBC driver on WildFly for use with Data Collections in RSA Identity Governance & Lifecycle RSA Authentication Manager 8.8 Setup and Configuration Guide Artifacts to gather in RSA Identity Governance & Lifecycle
Don't see what you're looking for?