26 lines
2.3 KiB
HTML
26 lines
2.3 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>Configure SSL for Web servers</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h4><a name="secjssws"></a>Configure SSL for Web servers</h4>
|
||
|
|
|
||
|
|
<p>Configuring SSL for the Web server depends on the type of Web server. Consult your Web server documentation for instructions.</p>
|
||
|
|
|
||
|
|
<p>Generally speaking, when SSL is enabled, an SSL key file is required. This key file should contain both the CA certificates (signer certificates) as well as any client or server certificates. Client authentication can also be enabled; by default, it is disabled.</p>
|
||
|
|
|
||
|
|
<p>When SSL client authentication is enabled in the Web server, the client certificate (the certificate from the browser) is forwarded by the WebSphere Web server plug-in to WebSphere Application Server - Express. When application deployment descriptors specify that client certificate authentication method is used, the application server accepts the forwarded certificate as authentication credentials if the distinguished name attribute of the certificate can be mapped to a principal in the user registry. For more information about mapping client certificates, see <a href="seccldfi.htm">Configure LDAP search filters</a>.</p>
|
||
|
|
|
||
|
|
<p><strong>Note:</strong> The client certificate is forwarded to the application server, regardless of whether SSL is enabled on the plug-in transport. Because SSL authentication of the browser client certificate actually occurs in the Web server, it is strongly recommended that you configure SSL in the plug-in transport. This requires client authentication of the plugin itself when application deployment descriptors specify the use of the client certificate authentication method, and thus, the possibility of receiving a client certificate from an untrusted source is eliminated. For more information about configuring the plug-in transport to require SSL client authentication, see "Configuring SSL for the application server's HTTPS transport" in <a href="secjsswa.htm">Configure SSL for WebSphere Application Server</a>.</p>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|