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 Orphan Summary 10Number of Views RSA Governance & Lifecycle Recipes: Report - AD Orphan Accounts 25Number of Views Partially orphaned accounts occur in RSA Identity Governance & Lifecycle when the ADC defines multiple user resolution att… 73Number of Views RSA Governance & Lifecycle Recipes: Chart - Application - Application Account & Orphan Trending 13Number of Views Another Mapping already exists for the target account attribute warning in RSA Identity Governance & Lifecycle when settin… 69Number 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 Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU 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
Don't see what you're looking for?