Oracle Fusion Middleware Documentation > Oracle WebLogic Server 12.1.3.0 Documentation > Administration Console Online Help > Configure a custom host name verifier

Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Configure a custom host name verifier

Before you begin

To write a custom host name verifier, see Using a Custom Hostname Verifier.


If you write a custom host name verifier, the class that implements the host name verifier must be specified in the CLASSPATH of WebLogic Server (when acting as an SSL client) or a stand alone SSL client.

When you use stand alone SSL clients, a custom host name verifier must be specified on the command line using the following argument or via the API:

-Dweblogic.security.SSL.HostnameVerifier=classname

where classname specifies the implementation of the weblogic.security.SSL.HostnameVerifier interface.

To configure a custom host name verifier:

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. In the left pane of the Console, expand Environment and select Servers.
  3. Click the name of the server for which you want to configure a host name verifier.
  4. Select Configuration > SSL , and click Advanced at the bottom of the page.
  5. Set the Hostname Verification field to Custom Hostname Verifier.
  6. Enter the name of the implementation of the weblogic.security.SSL.HostnameVerifier interface in the Custom Hostname Verifier field.
  7. Click Save.
  8. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).

After you finish

All the server SSL attributes are dynamic; when modified via the Console, they cause the corresponding SSL server or channel SSL server to restart and use the new settings for new connections. Old connections will continue to run with the old configuration. To ensure that all the SSL connections exist according to the specified configuration, you must reboot WebLogic Server.


Back to Top