Click the Expand icon next to the SSL Communication Between Web Cache and

Configuring Security 5-13 The Ports Configuration page displays.

b. Click Create.

The Create Port page appears.

c. From the Port Type list, select the port type, ADMINISTRATION,

INVALIDATION , or STATISTICS.

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. - ANY to represent any IP address

e. In the Port field, enter the listening port from which Oracle Web Cache

receives client requests for the Web site. Ensure that this port number is not in use. Port numbers less than 1024 are reserved for use by privileged processes on UNIX. To configure Oracle Web Cache to listen on a port less than 1024, such as on port 80, run the Oracle Web Cache webcached executable with the root privilege. If the webcached executable is not run as root, Oracle Web Cache fails to start. See Section 5.9 for instructions on changing the webcached executable to run as root.

f. Click OK.

3. Enable the port for SSL:

a. From the Web Cache menu, select Security SSL Configuration.

The SSL Configuration page displays.

b. Select the row for the endpoint you created in Step 2 and click Edit.

The Edit Port page displays.

c. In the SSL Configuration section, click Enable SSL.

d. In the Server Wallet Name field, select the wallet you created in

Section 5.4.1 . e. In the Advanced SSL Settings section, click Expand + to expand the configuration settings:

f. From the SSL Authentication list, select the type of client authentication.

- Server Authentication: A server authenticates itself to a client. - Mutual Authentication: A client authenticates itself to a server and that server authenticates itself to the client. - No Authentication: Neither server nor client are required to authenticate. - Optional Client Authentication: The server authenticates itself to the client, but the client may or may not authenticate itself to the server. Even if the client does not authenticate itself, the SSL session still goes through.

g. From the SSL Protocol Version list, select the version of SSL to use.