Last updated on MAY 24, 2017
Applies to:Oracle WebLogic Server - Version 8.1 to 10.3.6
Information in this document applies to any platform.
***Checked for relevance on 7-Aug-2013***
This article provides detailed steps to configure Apache HTTP Server with SSL in a WLS environment when using the WLS Proxy Plugin 1.0 with Open SSL.
This is not applicable to WLS Proxy Plug-In 1.1 aka Oracle Fusion Middleware 11.1.1x or 12c. The new plugin uses a mod_wl.so file and a new Oracle SSL implementation. See <Note 1384737.1>, "How To Configure SSL Between Apache 1.1 Plug-in And WebLogic Server, Using Self Signed Wallets" and <Note 1111903.1> , "WebLogic Server Proxy Plug-In Support".
If using the Oracle HTTP Server 11g or 12c, then it is using mod_wl_ohs and can follow one of the following depending on the desired topology:
<Note 1268723.1> Configuring Mod_wl_ohs to use SSL between Oracle HTTP Server and Weblogic Server in FMW 11g (11.1.1.X)
<Note 1665711.1> How to Configure mod_wl_ohs to use SSL between Oracle HTTP Server (OHS) and Oracle WebLogic Server (12.1.X) in Fusion Middleware 12c
<Note 1569732.1> How to Terminate SSL at LBR, Another HTTP Server, Web Cache or OHS 11g When Using WLS Plugin (mod_wl_ohs)
Using the WLS Proxy Plugin 1.0, the following steps will successfully setup SSL communication between the client (browser) and the Apache Web Server as well as SSL (https) communication between the Apache Web Server and the WebLogic Server.
At a high level, the following steps are implemented:
- Create a valid certificate from Verisign.
- Configure Apache plugin to use SSL using the new certificate.
- Configure WLS to use the new certificate.
- Test SSL proxy request to WLS.
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