How a Multi-App Entitlement Collector (MAEDC) resolves entitlement relationships with accounts and groups collected by a Multi-App Account Collector (MAADC)
Originally Published: 2019-11-19
Article Number
Applies To
RSA Version/Condition: 7.x
Issue
Resolution
Currently the MAEDC does not collect enough information about the entitled object (account/group) to know specifically which business source it is from. Consider the scenario where a MAEDC collects an entitlement for an Admin account. If the MAADC collects multiple Admin accounts for various business sources (applications), without this restriction the entitlement would resolve to ALL the Admin accounts collected across all the applications.
To handle the situation where an entitlement needs to be mapped to accounts and/or groups in multiple applications, create an Entitlement Data Collector (EDC) for the business source of the entitlement which can then use the standard resolution rules to have the entitlement applied to accounts and groups in multiple business sources.
Related Articles
Multi-app Entitlement Data Collector (MAEDC) fails with DuplicateNameException in RSA Identity Governance & Lifecycle Number of Views How to configure a JSON response in AFX connector capabilities to parse single or multi-valued responses in RSA Identity G… Number of Views Troubleshooting Wildfly clustering Multi-cast connectivity for RSA Via Lifecycle and Governance Number of Views 'Multi App Collector : 'Admin' privilege does not allow editing of the collector definition as expected in RSA Identity Go… Number of Views How (and why) do I enable Authentication Manager Prime multi-tenant mode? Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) Artifacts to gather in RSA Identity Governance & Lifecycle RSA Governance & Lifecycle 8.0.0 Administrators Guide RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?
