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
RSA Governance & Lifecycle Recipes: Chart - Application - Application Orphan Summary 10Number of Views RSA Governance & Lifecycle Recipes: Report - AD Orphan Accounts 25Number of Views RSA Governance & Lifecycle Recipes: Overview - Exploded Entitlements 9Number of Views Partially orphaned accounts occur in RSA Identity Governance & Lifecycle when the ADC defines multiple user resolution att… 73Number of Views RSA Identity Governance and Lifecycle - Novell eDirectory Connector Datasheet 11Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?