OBIEEintermediate

Security Model: Authentication & Authorization

Distinguish authentication (who you are) from authorization (what you can see/do) in OBIEE, and how Application Roles, groups, and RPD security tie together.

OBIEE security is layered, and interviewers use it to test whether you understand enterprise identity concepts, not just OBIEE clicks. Authentication answers "who are you?" and is typically delegated to WebLogic's security realm — backed by the embedded LDAP, an external LDAP/Active Directory, or SSO (SAML/Kerberos/OAM). Authorization answers "what can you see and do?" and is where OBIEE-specific concepts like Application Roles, Catalog Groups, and RPD-level data security come in.

It's like a building badge system: reception (WebLogic) checks your ID and knows which department you're in; your badge (Application Role) then decides which floors (subject areas) the elevator will even show you, and which filing cabinets (rows of data) on that floor you're allowed to open.

Key Concepts

1
The standard flow: a user authenticates against the configured identity store, WebLogic issues a subject with group memberships, and OPSS (Oracle Platform Security Services) maps those groups to Application Roles (e.g., BIConsumer, BIAuthor, BIAdministrator, or custom roles like SalesManagerRole). Application Roles are then referenced in two places: the RPD's security manager (for data-level filters, object permissions on presentation tables/columns, and query limits) and the Presentation Catalog (for folder/dashboard visibility permissions).
Application RolesBIConsumerBIAuthorBIAdministratorSalesManagerRole
2
Row-level (data) security is implemented in the RPD as data filters attached to Application Roles at the business model or presentation layer — a filter like "Sales"."Region" = VALUEOF(NQ_SESSION."REGION") restricts rows returned to whatever the session variable resolves to for that user. Object-level security (which subject areas, tables, or columns a role can even see) is set via the Identity Manager in the Administration Tool. Getting this right in an interview means clearly separating: WebLogic/OPSS (authn + role mapping) → RPD (data security + object permissions) → Catalog (content visibility).
data filters"Sales"."Region" = VALUEOF(NQ_SESSION."REGION")