Entitlement View does not scope correctly when triggered via request buttons in RSA Identity Governance & Lifecycle
Originally Published: 2019-01-08
Last Modified: 2023-11-30
Article Number
Applies To
RSA Version/Condition: 7.0.2, 7.1.0
Issue
Whenever an Entitlement View is used to request access for a user (that is triggered via a request button) the setting Initial set of entitlements to show: Matching (roles that user matches the role membership rule) from the entitlement view is ignored. While if the default request button is used the entitlement setting is not ignored and the shown entitlements are scoped correctly.
How it looks via the Entitlement View Preview option
How it looks via the Add Entitlement option
How it looks using the “Add using request sources” button
It ignores the filter of showing only the roles the user matches the membership rule but instead shows all the roles.
Cause
Resolution
Related Articles
Is there a way to enforce passphrase to certificates requested by user with RCM ? 6Number of Views Is there a way to list all issued certificates in RSA Certificate Manager? 20Number of Views Why do authentication errors occur when performing a SecurID Access Authentication Manager test? 89Number of Views Is there a way to disable logging for the ACE/Server Administration API to the system logs 3Number of Views Is there a way to auto-populate the subjectAltNames extension with user's email address? 13Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Patch Updates RSA Authentication Manager Upgrade Process RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities
Don't see what you're looking for?