Leveraging Oracle Identity Management Infrastructure

5-8 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache

1. From Oracle Web Cache Manager, in the navigator frame, select Properties

Security . See Section 2.7.2 . The Security page appears.

2. In the Security page, click Change Trusted Subnets under the Current Trusted

Subnets. The Change Trusted Subnets dialog box appears. 3. Select an option: All subnets: Allows requests from all computers in all the subnets in the network. This machine only: Allows requests from only this computer. Enter list of IP addresses: Allows requests from all IP addresses you enter in a comma-delimited list. You can enter IP addresses in using these format: – Complete IP address in dot notation, including the network number, subnet address, and unique host number Example: 10.1.0.0 – Networknetmask pair for subnet restriction through masking Example: 10.1.0.0255.255.0.0 allows all the hosts in the 10.1 subnet access. – Networknnn Classless Inter-Domain Routing CIDR specification to require nnn bits from high end to match Example: 10.1.0.016 allows all the hosts in the 10.1 subnet access. This example is similar to the networknetmask example, except the netmask consists of nnn high-order 1 bits.

4. Click Submit.

5. Restart Oracle Web Cache using opmnctl. See Section 2.13.1 .

5.4 Configuring Oracle Web Cache for HTTPS Requests

To provide more security for your Web site, you can configure Oracle Web Cache to receive HTTPS protocol client requests and send HTTPS requests to the origin server. HTTPS uses SSL to encrypt and decrypt user page requests as well as the pages that are returned by the Oracle Web Cache and origin servers. You can also configure Oracle Web Cache to send traffic to the origin server through an HTTPS listening port. To configure HTTPS support for Oracle Web Cache, perform these tasks: ■ Section 5.4.1, Task 1: Create Wallets ■ Section 5.4.2, Task 2: Configure an HTTPS Listening Port ■ Section 5.4.3, Task 3: Configure SSL Settings for Oracle Web Cache Connections to Origin Servers ■ Section 5.4.4, Task 4: Configure a Site to Require HTTPS Requests ■ Section 5.4.5, Task 5: Restart Oracle Web Cache ■ Section 5.4.5, Task 5: Restart Oracle Web Cache ■ Section 5.4.6, Task 6: Perform Additional Configuration for Oracle WebLogic Servers Configuring Security 5-9

5.4.1 Task 1: Create Wallets

To support HTTPS for Oracle Web Cache, you must create a wallet on the Oracle Web Cache server for each supported site. You need wallets to support the following HTTPS requests: ■ Client requests for sites hosted by Oracle Web Cache ■ Administration, invalidation, and statistics monitoring requests to Oracle Web Cache ■ Oracle Web Cache requests to origin servers, as well as admin server process requests for requests to invalidation and statistics monitoring ports enabled for SSL For each site that Oracle Web Cache supports, configure at least one wallet. You specify the location of the wallet for each of the Oracle Web Cache HTTPS listening and operations ports to support incoming HTTPS requests, and the origin server to support outgoing HTTPS requests. You can share one wallet, or you can create separate wallets. If you use the same wallet, keep in mind that it can support only one server-side certificate. To create a wallet:

1. Navigate to the Web Cache Home page in Fusion Middleware Control. See

Section 2.6.2 .

2. From the Web Cache menu, select Security and then Wallets.

The Wallets page displays.

3. Perform the tasks in section Create a Wallet of the Oracle Fusion Middleware

Administrators Guide.

5.4.2 Task 2: Configure an HTTPS Listening Port

To configure HTTPS protocol support between client and Oracle Web Cache, you must configure an HTTPS listening port for Oracle Web Cache. To add an HTTPS listening port: 1. Navigate to the Web Cache Home page in Fusion Middleware Control. See Section 2.6.2 . 2. Create the listening port:

a. From the Web Cache menu, select Administration Ports Configuration.

The Ports Configuration page displays.

b. Click Create.

The Create Port page appears.

c. From the Port Type list, select NORM.

d. In the IP Address field, specify the computer running Oracle Web Cache:

- IP version 4 address written in a 32-bit dotted decimal notation or an IP version 6 address written in a 128-bit notation. See Section 2.5 . - A host name that resolves to an IP address of the computer running Oracle Web Cache. If you do not want to rely on Domain Name System DNS to resolve the host name, use a different name resolution mechanism, such as the UNIX etchosts file.