Data Access Collector (DAC) rejects Account Relationships when collecting Account Permissions in RSA Identity Governance & Lifecycle
Originally Published: 2016-06-10
Last Modified: 2023-10-06
Article Number
Applies To
RSA Version/Condition: All
Issue
EC[170] Context[RunID=###,EDC(Name=<name of DAC Collector>,ID=XXX,APP=XXX)]Message[Entitlement
Data Validation: User Entitlement Data is invalid
(caused by prior validation error.Invalid user/group/account or invalid/duplicate resource/application role]
The DAC is defined to collect Account Permissions (Collectors > Data Access Collectors > Create Data Access Collector > Data Source Type: Database) as follows:
Cause
The account resolution for the DAC has not been defined:
Resolution
Define the Target Account Collector (ADC) used to collect the accounts that have access to the entitlements collected by the DAC and define an Account Attribute to be used to correlate the accounts collected by the ADC with the account entitlements collected by the DAC. For example,
Related Articles
View User Aliases Associated with a RADIUS Profile 9Number of Views RSA Governance & Lifecycle Recipes: Account Review - Revoke Account Options 74Number of Views RSA Identity Management and Governance account name not available when viewing the results of user access review 32Number of Views When should a Provisioning-Termination Rule delete accounts in RSA Identity Governance & Lifecycle? 198Number of Views How to interpret the RSA Identity Governance & Lifecycle User Access Review User Entitlement Coverage report. 41Number 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?