Entitlement View does not scope correctly when triggered via request buttons in RSA Identity Governance & Lifecycle
Originally Published: 2019-01-08
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
How to remove unnecessary tables from database statistics analysis in RSA Identity Governance & Lifecycle 97Number of Views Performance Implications of database statistics computed on GTT* tables 55Number of Views Generic REST Collector fails with 'jsonpath.PathNotFoundException:Missing property in path $['members']' error collecting … 80Number of Views Unable to edit Role Membership Rule in RSA Governance & Lifecycle 35Number of Views When 'Generate Indirect Entitlements' is disabled for Roles, Technical and Global Role Entitlements are still granted to R… 59Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory Mandatory Certificate Upgrade Required by 6th October 2025 for RSA MFA Agent for PAM, RSA MFA Agent for Apache, and Third … RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?