Modify ssl.conf for Keep-Alive Connections

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.

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

h. Click OK.

5.5.2 Requiring Client-Side Certificates

You can require that clients send certificates client-side certificates to the cache to verify the identity of the client. With client-side certificates, the client browser sends the certificate to the cache during the SSL handshake. Then, the server processes the request for the object. If the requested object is not stored in the cache, the cache forwards the request to the application Web server, a peer cache in a cluster, or a subordinate cache in a hierarchy. To transfer information about the client-side certificate to another cache or to the application Web server, Oracle Web Cache adds HTTP headers to the request. The headers begin with the string SSL-Client-Cert. Note the following points about using client-side certificates: ■ In a simple configuration client to cache to application Web server, the client sends the certificate to the cache during the SSL handshake. If the requested object is not stored in the cache, the cache forwards the request to the application Web server and transfers the client-side certificate information in headers to the application Web server. The application Web server recognizes the headers and responds to the request. ■ In a cluster, the client sends the certificate to a cache cluster member during the SSL handshake. If the requested object is not stored in that cache, the cluster member requests it from a peer the cluster member that owns the object. With client-side certificates, Oracle Web Cache must be able to pass the client-side certificate information in headers to the peer cluster member, and the peer must be able to pass the headers to the application Web server. ■ If a site requires client certificates, then a 403 Forbidden error returns if a client certificate is not provided. If a listen port requires client certificates, then the SSL handshake fails if a client certificate is not provided. The following topics describe how to configure client-side certificate settings: ■ Section 5.5.2.1, Configuring Client-Side Certificate Settings for the HTTPS Listening Ports ■ Section 5.5.2.2, Configuring Client-Side Certificate Settings for Cache Clusters ■ Section 5.5.2.3, Configuring Client-Side Certificate Settings for a Site

5.5.2.1 Configuring Client-Side Certificate Settings for the HTTPS Listening Ports

To use client-side certificates, you must enable an HTTPS listening port, as described in Section 5.4.2 . If you have a cache cluster, you must enable HTTPS listening ports for all cluster members. In addition, you must configure Oracle Web Cache to require client browsers to provide SSL certificates. Note: Oracle Web Cache supports the use of client-side certificates with Oracle HTTP Server only. Oracle Web Cache does not support client-side certificates with a distributed cache hierarchy because the security of the certificates cannot be guaranteed.