Partially orphaned accounts occur in RSA Identity Governance & Lifecycle when the ADC defines multiple user resolution attributes from the same target collector
Originally Published: 2019-05-01
Article Number
Applies To
RSA Version/Condition: 7.0.2, 7.1.0
Issue
Partially orphaned accounts are created after Unification. In the example below, note that UserC3 is not displayed as an orphaned account, yet it is not mapped to any user which is the definition of an orphaned account.
Cause
As an example, an IDC collects User Id, Email Address, and Department. An ADC collects AccountName. Three User Resolution rules are defined on these IDC attributes in the ADC definition:
After running the IDC, Unification and ADC, the AccountName resolves to the User Id and correctly maps the users.
If one of the user attributes other than the User Id is modified in the IDC, the problem occurs. In this case, the email address for UserC3 was modified. After running the IDC and Unification, the account is left partially orphaned:
Resolution
Workaround
Related Articles
RSA Governance & Lifecycle Recipes: Chart - Application - Application Orphan Summary 10Number of Views RSA Governance & Lifecycle Recipes: Telemetry Chart - Total Collectors 13Number of Views RSA Governance & Lifecycle Recipes: Report - AD Orphan Accounts 25Number of Views RSA Governance & Lifecycle Recipes: AFX Telemetry - Total Connectors 27Number of Views Manually unmapped accounts are not rejected in the collection and remain as an Orphan accounts in RSA Governance & Lifecycle 73Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to Download OTP Token Seed Files from myRSA Installing a new license on RSA Authentication Manager RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?