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 Multi-App Collector Circuit Breaker trips incorrectly in SecurID Governance & Lifecycle Number of Views Multi-App Entitlement Data Collector (MAEDC) fails with ORA-30926 if two MAEDCs overlap in Application Name and Internal I… Number of Views Generic REST EDC collector not getting the desired results in entitlement relationship in RSA Governance & Lifecycle Number of Views Some OOTB App Metadata Collector fields are missing in the Application table options in RSA Identity Governance & Lifecyle Number of Views
Trending Articles
RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to Upgrade Internal SHA-1 Certificates to SHA-256 in Authentication Manager Using rsautil RSA Authentication Manager 8.9 Setup and Configuration Guide RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows
Don't see what you're looking for?
