40 lines
3.6 KiB
HTML
40 lines
3.6 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 trusted mode for the internal HTTP transport</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h3><a name="secctmint"></a>Configure trusted mode for the internal HTTP transport</h3>
|
||
|
|
|
||
|
|
<p>WebSphere Application Server - Express has further tightened security by introducing a configuration option that permits administrators to specify if they trust private HTTP headers or not. You should carefully evaluate enabling the WebSphere Application Server - Express internal HTTP transport in the trusted mode in the production environment to determine if sufficient trust is established.</p>
|
||
|
|
|
||
|
|
<p>When the trusted mode is enabled, the WebSphere Application Server - Express internal HTTP transport allows the assertion of the user identity by adding the client certificate to the HTTP header. The Web server plug-in can use this feature to support client certificate authentication. The HTTP header does not contain any information that WebSphere Application Serve - Express can use to detemine the server identity which asserts the client certificate. You should establish a secure communication channel with transport level authentication between the Web server plug-in and WebSphere Application Server - Express to avoid HTTP header spoofing.</p>
|
||
|
|
|
||
|
|
<p>You can configure the trusted mode for each HTTP port independently and disable on any port that client machines can access directly, both from the Internet and the intranet. Requiring the Web server plug-in to establish a Secure Sockets Layer (SSL) connection with client certificate authentication ensures that only a trusted Web server plug-in asserts the user certificate. Moreover, you should use a self-signed certificate so that only those servers that have the self-signed certificate can establish a secure connection to the trusted internal HTTP transport. For more information on setting up the SSL connection with self-signed certificate authentication, see <a href="secjsswa.htm">Configure SSL for WebSphere Application Server - Express</a>.</p>
|
||
|
|
|
||
|
|
<p>Other than SSL, you can use mechanisms such as Virtual Private Network (VPN) and IPSec to protect the internal HTTP transport from being accessed by unauthorized users.</p>
|
||
|
|
|
||
|
|
<p>The trusted mode is set to <tt>true</tt> by default. Perform the following steps in the WebSphere administrative console to add a custom transport property to disable the trusted mode:</p>
|
||
|
|
|
||
|
|
<ol>
|
||
|
|
<li>Expand <strong>Servers</strong>, and click <strong>Application Servers</strong>.</li>
|
||
|
|
<li>Click your application server name.</li>
|
||
|
|
<li>Click <strong>Web Container</strong> --> <strong>HTTP Transports</strong> --> <strong><em>host_name</em></strong> --> <strong>Custom Properties</strong>, where <em>host_name</em> is the host name of your server.</li>
|
||
|
|
<li>Click <strong>New</strong> and enter the property name <tt>Trusted</tt> with the value of <tt>false</tt>.</li>
|
||
|
|
<li>Restart the server.</li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
<p>After the server restarts, the transports for which you set trusted to <tt>false</tt> do not accept client certificate assertion. An HTTP Error 403 is returned with the error message similar to the following in your log file:</p>
|
||
|
|
<pre> Requests through proxies such as the WebSphere webserver plug-in are not permitted
|
||
|
|
to this port. The HTTP transport on port 9080 is not configured to be trusted.</pre>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|