How to Use the Channel Setting and Virtual Host Setting to Make Two Way SSL Effective Only on the Virtual Host
(Doc ID 2128931.1)
Last updated on MARCH 07, 2019
Applies to:Oracle WebLogic Server - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
To use Virtual Hosts to control the below scenario:
- There is only one Managed Sever named Server1
- An application deployed on the Server
- When the application is accessed from the URL mentioned in Scenario 1 below - the client certificate should be checked to confirm that it was created by a Certificate Authority the server trusts
- If the application is accessed from the URL in Scenario 2 below - the client certificate will not be checked
- User A sends the request to server Server 1 using URL (e.g https://servername:7002/jspsimple/login.jsp)
- It must check the client certificate (two way SSL)
NOTE: In the URL above, servername is the virtual host name representing the localhost. The IP address is different from the IP address used in Scenario 2
- User B sends a request to server Server1 Using URL(e.g https://xx.xx.xx.xx:7002/jspsimple/login.jsp)
- It will not check the client certificate (one way ssl)
NOTE: xx.xx.xx.xx is the real IP address like 10.182.155.106
Both of these scenarios can be configured by setting up the [Virtual Host] and [Channel] correctly.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|1. Create two way SSL (If this was done previously, this step can be skipped)|
|1.1 Configure WebLogic Server for One-Way SSL|
|1.2 Two-way setup: Import the Trusted CA into the Keystore (e.g. create the client certificate)|
|1.3 Configure Client Authentication for Weblogic|
|1.4 Test you can access Weblogic via SSL|
|2. Confirm one-way SSL is configured for the server|
|3. Create network channels (e.g channel-0) for the use of two-way SSL(client-certificate-enforced)|
|4, create a virtual host of WebLogic Server and set the network-access-point created in step 3|