Total Orphaned Accounts count is not getting updated after local account mapping import in RSA Identity Governance & Lifecycle
Originally Published: 2018-03-22
Article Number
Applies To
RSA Version/Condition: 7.0.1, 7.0.2
Issue
Steps to reproduce
- Import account mappings for a particular application under Application > Collectors.
- Click on the account collector then on Accounts > Import Account Mappings.
- Hover over Application > Accounts > Orphan tab. You can see the Orphan account count as 2.
- Hover over the General tab. You can still see the old value.
- Once you run the application account collector the correct count gets updated.
Cause
Resolution
Workaround
Related Articles
RSA Governance & Lifecycle Recipes: Chart - Application - Application Account & Orphan Trending 12Number of Views RSA Governance & Lifecycle Recipes: Report - AD Orphan Accounts 18Number of Views Account summary table export includes the HTML tags that construct the account mapping button in RSA Identity Governance &… 38Number of Views Failure to map other accounts collected by MAADC, Only the first collected account is mapped in RSA Governance & Lifecycle 86Number of Views Manually unmapped accounts are not rejected in the collection and remain as an Orphan accounts in RSA Governance & Lifecycle 72Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide How to recover the Application and AFX after an unexpected database failure in RSA Identity Governance & Lifecycle RSA MFA Agent 2.4 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Upgrade Process
Don't see what you're looking for?