Data Filters and Permissions Defined At the User Level In The Repository Do Not Take Effect in OBIEE 12c (12.2.1)
(Doc ID 2087268.1)
Last updated on APRIL 10, 2017
Applies to:Business Intelligence Suite Enterprise Edition - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 12g]
Information in this document applies to any platform.
Data filters and Object permissions defined in the repository (RPD) at the user level; however, when running an analysis | report ,the user still can access and see data that they are not supposed to see based on permissions and filters defined.
Steps to reproduce in SampleApp:
- Create a new user called testuser and assign BIConsumer application role.
- Define data filter :Login to repository via the Administration Tool online mode and select this user under Manage > Identity, click permissions and set a data filter based on year column to only see 2010 year data
- Define object permission: Select any presentation column (e.g. - Billed Quanity) and click permissions, select you user (e.g. - testuser) and configure No Access to true.
- Login as testuser and run a report with year and billed quantity columns. All data for years is available when only 2010 is supposed to be shown and billed quantity should be hidden, but is displayed.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document