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
Rules are not triggered after unification run in RSA Identity Governance & Lifecycle 80Number of Views When multi-step review is generated, NewReviewGeneratedEvent is triggered twice for second step review sending duplicate e… 49Number of Views Review escalation workflows do not trigger if review is set to Hold by an escalation workflow after due date in RSA Identi… 61Number of Views When 'Generate Indirect Entitlements' is disabled for Roles, Technical and Global Role Entitlements are still granted to R… 59Number of Views Generic REST Collector fails with 'jsonpath.PathNotFoundException:Missing property in path $['members']' error collecting … 80Number of Views
Trending Articles
Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA Authentication Manager Upgrade Process RSA Authentication Manager Patch Updates How to Download OTP Token Seed Files from myRSA RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?