Configuring SSL for Oracle SOA Suite

Configuring SSL in Oracle Fusion Middleware 6-23 complete the manual procedure described in Oracle Fusion Middleware Publishing Reports to the Web with Oracle Reports Services.

6.5.5.2 SSL for Oracle Forms

To SSL-enable Oracle Forms, you need to enable SSL on the components front-ending Oracle WebLogic Server. For example, if you have an Oracle HTTP Server and an Oracle Web Cache front-ending the Oracle WebLogic Server that hosts Oracle Forms, you need to configure the following: ■ Inbound SSL for Oracle Web Cache See Section 6.4.2.1, Enable Inbound SSL for Oracle Web Cache Using Fusion Middleware Control. ■ Inbound SSL for Oracle HTTP Server See Section 6.4.3.1, Enable SSL for Inbound Requests to Oracle HTTP Server Virtual Hosts Using Fusion Middleware Control. ■ Inbound SSL for Oracle WebLogic Server See Section 6.5.1.1, Inbound SSL to Oracle WebLogic Server. ■ SSL between Oracle Web Cache and Oracle HTTP Server See Section 6.4.2.3, Enable Outbound SSL for Oracle Web Cache Using Fusion Middleware Control. ■ SSL between Oracle HTTP Server and Oracle WebLogic Server See Section 6.4.3.3, Enable SSL for Outbound Requests from Oracle HTTP Server.

6.5.5.3 SSL for Oracle Discoverer

Running Oracle Discoverer over https requires certain tasks such as enabling SSL for the Oracle HTTP Server virtual host and Oracle Web Cache front-ending the Oracle WebLogic Server that hosts Oracle BI Discoverer, among others. For details, see Configuring End-to-End Secure Sockets Layer for Discoverer in the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer.

6.5.5.4 SSL for Oracle Portal

Oracle Portal uses a number of different components such as the Parallel Page Engine, Oracle HTTP Server, and Oracle Web Cache each of which may act as a client or server in HTTP communication. As a result, each component involving Oracle Portal in the middle tier is individually configured for https. For details, see the Oracle Fusion Middleware Administrators Guide for Oracle Portal. Note: These steps are necessary only if you wish to set up end-to-end SSL. In most cases, it is sufficient to enable SSL only on the first component getting the request, since the other components are usually within the intranet. For example, if the request is sent to Oracle Web Cache, you may only need to follow the first step. If the request is sent to Oracle HTTP Server, you may only need to follow the second step. Select the steps as dictated by your topology. 6-24 Oracle Fusion Middleware Administrators Guide

6.5.6 Client-Side SSL for Applications

For information on how to write SSL-enabled applications, see Using SSL Authentication in Java Clients in Oracle Fusion Middleware Programming Security for Oracle WebLogic Server. For best practices, refer to Section 6.8.2, Best Practices for Application Developers.

6.6 Configuring SSL for the Data Tier

This section contains these topics: ■ Enabling SSL on Oracle Internet Directory Listeners ■ Enabling SSL on Oracle Virtual Directory Listeners ■ Configuring SSL for the Database

6.6.1 Enabling SSL on Oracle Internet Directory Listeners

Out of the box, Oracle Internet Directory nodes are SSL-enabled in no-auth mode. This section explains how to SSL-enable Oracle Internet Directory listeners using Fusion Middleware Control and the WLST command-line tool.

6.6.1.1 Enable Inbound SSL on an Oracle Internet Directory Listener Using Fusion Middleware Control

In this example, the following steps enable SSL in no-auth mode for an instance of Oracle Internet Directory using Fusion Middleware Control: 1. Select the Oracle Internet Directory instance in the navigation pane on the left. 2. Navigate to Oracle Internet Directory, then Administration, then Server Properties . 3. Click Change SSL Settings. 4. On the SSL Settings dialog: