Secured Oracle HTTP Server: Configuring SSL

In a previous post we explained how an Enterprise OBIEE 11g environment can be secured when deploying OBIEE 11g content outside the organization by placing an Oracle HTTP Server (OHS) into the DMZ side firewall. In this new post we will describe the steps needed to configure the OHS to redirect traffic from outside the DeMilitarized Zone (DMZ) using a secured HTTP communication with Secure Sockets Layer (SSL).

 

The following graph describes the environment:

 

 

How to secure an Enterprise OBIEE 11g environment: the Oracle HTTP Server

Most clients have their Oracle Business Intelligence Enterprise Edition (OBIEE) 11g environment inside their Local Area Network (LAN) secured behind two firewalls, one between the World Wide Web (WWW) and the DeMilitarized Zone (DMZ) and another one between the DMZ and their LAN as it can be seen in the following graph.

 

E-Business Suite authentication for BI Publisher

Think about an Oracle BI Applications environment built on top of Oracle Business Intelligence Enterprise Edition (OBIEE) in which the source system is the Oracle E-Business Suite (EBS), the access to OBIEE has been integrated with the E-Business Suite so when a user logs into the EBS system he has the rights to access OBIEE analytics without being prompted for user and password. Everything works fine until someone decides to click on the “Report” link that belongs to the “Published reporting” (BI Publisher) and gets an error message indicating that the current user has no privileges to access it.

This guide contains the steps that need to be applied in order to integrate BI Publisher user authentication interface with EBS, so a user will be able to access the OBIEE (BI Publisher) environment if this user exists as an EBS user with the correct responsibilities assigned.