Is SSLHonorCipherOrder and TLS 1.1/1.2 Supported for Oracle HTTP Server? (Doc ID 1485047.1)

Last updated on SEPTEMBER 20, 2017

Applies to:

Oracle HTTP Server - Version 10.1.2.0.2 to 10.1.3.5.0 [Release AS10gR2 to AS10gR3]
Oracle Fusion Middleware - Version 10.1.2.0.0 to 10.1.4.3.0 [Release AS10gR2 to AS10gR3]
Web Cache - Version 10.1.2.0.2 and later
Oracle Fusion Middleware - Version 12.1.2.0.0 and later
Oracle Security Service - Version 10.1.0.5 to 11.1.0.7 [Release 10.1 to 11.1]
Information in this document applies to any platform.

Goal

Overview

This document covers two issues because the question is about the support of SSLHonorCipherOrder and/or TLS 1.1 and 1.2. It is a popular request to check/configure these at the same time.

SSLHonorCipherOrder

As a security best practice, an administrator can choose to only allow newer/stronger SSL protocols and ciphers with the SSLProtocol and SSLCipherSuite directives. When choosing a cipher during an SSL handshake, normally the client's preference is used. If an SSLHonorCipherOrder directive is enabled, the server's preference will be used instead, allowing an administrator even more control over security. SSLHonorCipherOrder is an Apache directive which allows more control to an administrator.  The directive is available in Apache 2.1 and later, (if using OpenSSL 0.9.7 or later), as provided at the apache.org web site:

http://httpd.apache.org/docs/2.2/mod/mod_ssl.html#sslhonorcipherorder

When configuring this in the Oracle HTTP Server ssl.conf file, the Oracle HTTP Server fails to start saying it is not a valid directive.

 

TLS 1.1 and TLS 1.2

SSLHonorCipherOrder directive is more desirable when the older SSL 3.0 or TLS 1.0 protocols are used. Many administrators prefer to configure TLS 1.1 and 1.2.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms