Currently if you schedule DV bursting to a distribution list the row level security is not applied.
If distribution lists could be defined within OAC then it would identify the individual users and apply row level security during bursting
Interesting idea in the idea lab. I wonder if it's more of a bug, security topic or enhancement. + @Alan Lee - Oracle-Oracle and @Adam Bloom-Oracle . In any case, I voted for it. Thank you @Victor H
+ @Sandeep S. Chauhan-Oracle
The bursting feature is only supported for users selected from OAC identity management system. Row level security is defined at the user level. Even though a distribution list may contain email addresses that are the same as users in the IDM, there is no explicit mapping. The best way to send to a group of users for bursting is to include these users in custom app roles that sit inside IDM.
We will make this more clear in the documentation.
@Alan Lee - Oracle-Oracle Thanks Alan.
Is this something that can be achieved in the current version?
How would we define these custom app roles? If the distribution list is defined in the client email server. how will OAC know the individual users for row level security?
Yes, this is supported in the current release. You can create a custom app role by following documentation here: https://docs.oracle.com/en/cloud/paas/analytics-cloud/acabi/configure-what-users-can-see-and-do.html#GUID-7547E519-07B5-414A-B664-771BA753B2FB
Assign users that you want for the scheduled delivery. Then you can specify the app role in the recipient field of the schedule.
Thanks Alan , this is a useful workaround but creating roles is usually done by totally different users.
I think it is still needed to add distribution lists in OAC as their one separate object, We already have many shell roles for folder structure access and would prefer to minimize them.
OAS Classic Report Results display the first 5000 rows and the OAS user needs to click the next button for the next 5000 rows and so on. The 5000 row limit is the maximum allowed to be setup in the OAS Console. OBIEE Report Results support display of the entire report results data set. Our users would like this feature in…
Background We recently identified an issue through an inconsistency in the number of records returned in an API response. This allowed us to notice, after the fact, that a fix had been applied that changed the behavior of an existing API. Problem We understand that information about resolved bugs is eventually made…
We need a way for non-admin users to view the backend/physical SQL queries executed by reports (via Session and Query Logs) without granting them full administrator access. OAC's custom Application Role model (Console > Roles and Permissions) allows selecting fine-grained permissions instead of assigning predefined roles.…
Customer would like to request that IBM DB2 12.x be added as a supported data source for Oracle Analytics Server. They hope that it will be included as a certified and supported data source in the next(Year 2027 ) OAS release. Background: The customer is currently operating a reporting and analysis platform using Oracle…
We would like to restrict the MCP to certain OAC application roles instead of all the users. Please help us to achieve this functionality.
