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: Review Definition Types 12Number of Views RSA Governance & Lifecycle Recipes: Chart - Application - Application Shared Accounts 17Number of Views RSA Governance & Lifecycle Integration: Amazon Redshift Summary 32Number of Views RSA Governance & Lifecycle Recipes: Report - AD Orphan Accounts 26Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?