Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 2 · Security, roles and what you are allowed to see
Security for reporting: the part people miss
Lesson 17 of 177 · 2 min
Here is the part people miss, and it is the question a security reviewer will ask about your report. A BI Publisher data model built on your own SQL runs with the privileges of the REPORT, not of the person reading it. Row-level data security — the ledger and business unit gates from Lesson 3 — is applied by the application layer, and a query you wrote yourself does not necessarily pass through it. So a report can show a user rows they could never see in the UI. Sometimes that is exactly what is wanted. A group-level reconciliation, a payroll audit extract, a statutory return: these legitimately span everything, and the control is who can run the report rather than what the query returns. Say so explicitly when you build one, and put the report behind a role that matches the audience. And sometimes it is a leak with…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.
In this module: Module 2 · Security, roles and what you are allowed to see
- 1Roles, privileges and duties
- 2Data security versus function security
- 3Data access sets and business unit security
- 4The security diagnostic sequenceFree preview
- 5Reading the security console
- 6Security for reporting: the part people miss
- 7Custom roles: when, and how to survive an update
- 8Provisioning and role assignment at scale
- 9What breaks: the three security failures you will meet
- 10Lab briefing · Diagnosing three access failures