Manually unmapped accounts are not rejected in the collection and remain as an Orphan accounts in RSA Governance & Lifecycle
Last Modified: 2024-01-26
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
Partially orphaned accounts occur in RSA Identity Governance & Lifecycle when the ADC defines multiple user resolution att… 73Number of Views RSA Governance & Lifecycle Recipes: Report - AD Orphan Accounts 26Number of Views Total Orphaned Accounts count is not getting updated after local account mapping import in RSA Identity Governance & Lifec… 69Number of Views RSA Governance & Lifecycle Services 101: Dynamic Reports & Charts - What are they and how do you use them? 25Number of Views RSA Governance & Lifecycle Recipes: Dashboard - Admin Collector Summary 15Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme How to Change the Token Lifetime Extension Window in Authentication Manager Using rsautil RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Setup and Configuration Guide FAQ: RSA SecurID Appliance Transition (A450 to A450R2)
Don't see what you're looking for?