Manually unmapped accounts are not rejected in the collection and remain as an Orphan accounts in RSA Governance & Lifecycle
Article Number
Applies To
This is a known issue in the following versions:
- SecurID Governance & Lifecycle 7.5.2
- RSA Governance & Lifecycle 8.0
Issue
Manually un-mapped accounts should be rejected during the collection with the below error and not to be mapped again.
EC[383] Context[RunID=603, ADC(Name=MAADC Test Collector, ID=27)] Message[Account Data Validation: Collected Account to User mapping is manually unmapped.]
Sometimes, manually unmapped accounts are not rejected and remain as an Orphan accounts.
In the Accounts Tab the accounts are marked as Orphan accounts.
In the User Mapping Tab these accounts show under "Users that have been manually removed from accounts."
Cause
Resolution
- SecurID Governance & Lifecycle 7.5.2 P09
- RSA Governance & Lifecycle 8.0.0 P02
Related Articles
RSA Governance & Lifecycle Recipes: Chart - Application - Application Account & Orphan Trending 12Number of Views ASR fails to generate with an 'ORA-06502: PL/SQL: numeric or value error: character string buffer too small' error in RSA … 127Number of Views RSA Governance & Lifecycle Recipes: Report - AD Orphan Accounts 20Number of Views The display names of the 'Contains Privilege Access' and 'Business Criticality' attributes fail to change after they have … 61Number of Views Provisioning Termination rule is not generating change requests to disable accounts in RSA Identity Governance and Lifecycle 125Number of Views
Trending Articles
An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process How to install the jTDS JDBC driver on WildFly for use with Data Collections in RSA Identity Governance & Lifecycle
Don't see what you're looking for?