This blog series reviewing OBIEE security has to this point identified how users are defined and authenticated within WebLogic, the major security concerns with WebLogic and how application roles are defined and mapped to LDAP groups within Enterprise Manager. We will now review OBIEE authorization, how OBIEE determines what data users can see after they login.
The OBIEE Repository is comprised of three layers. A very simplistic summary is below:
- Physical layer: Defines all database or data source connections (user id and passwords are entered and stored here), the physical table and columns, primary and foreign key relationships.
- Business Model Mapping layer (BMM): Referencing the physical layer, here is where logical structures are built and aggregation rules are defined. The BMM is really the heart of an OBIEE application
- Presentation layer: Referencing the BMM, this layer presents the tables and columns to end users. For example, remove unwanted columns or rename awkwardly named columns.
Object and Data Level Security
Object (Physical layer) and Data (BMM) level security is defined within the identity manager in the Repository. Object security can be set to either allow or deny access to a physical table or column. Data security allows rules to be applied to logical tables or columns (BMM layer). These rules can use static values as well as session variables.
Navigation: Open identity manager within the RPD -> select user or role -> click on permissions
Presentation Layer Security Rule
If you have questions, please contact us at email@example.com
-Michael Miller, CISSP-ISSMP