50 lines
2.8 KiB
HTML
50 lines
2.8 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 global security</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h3><a name="seccfg"></a>Configure global security</h3>
|
||
|
|
|
||
|
|
<p>It is helpful to understand security from an infrastructure standpoint so that you know the advantages of different authentication mechanisms, user registries, authentication protocols, and so on. Picking the right security components to meet your needs is a part of configuring global security. For more information, see <a href="secglobal.htm">Global security</a>.</p>
|
||
|
|
|
||
|
|
<p>When you understand the security components, you can proceed to configure global security in WebSphere Application Server - Express.</p>
|
||
|
|
|
||
|
|
<p>Perform these steps:</p>
|
||
|
|
|
||
|
|
<ol>
|
||
|
|
<li><p><strong>Start the WebSphere administrative console.</strong>
|
||
|
|
<br>If security is currently disabled, log in with any user ID. If security is currently enabled, log in with a predefined administrative ID and password (this is typically the server user ID specified when you configured the user registry).</p>
|
||
|
|
|
||
|
|
<p>In left navigation menu of the administrative console, click <strong>Security</strong>.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong><a href="seccur.htm">Configure a user registry</a></strong>
|
||
|
|
<br>WebSphere security requires the a user registry, which is used to authenticate users to protected resources.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong><a href="seccamec.htm">Configure the authentication mechanism</a></strong>
|
||
|
|
<br>Configure the mechanism the WebSphere Application Server - Express uses to authenticate users.</p></li></p></li>
|
||
|
|
|
||
|
|
<li><p>(Optional) <strong><a href="seccsso.htm">Configure single signon</a></strong>
|
||
|
|
<br>If you configured LTPA as your authentication mechanism and your applications contain form-based login, you may want to configure single signon.</p></li>
|
||
|
|
|
||
|
|
<li><p>(Optional) <strong><a href="secctai.htm">Configure a trust association interceptor</a></strong>
|
||
|
|
<br>If you are using a third-party reverse-proxy server (such as WebSEAL) in your topology, see this topic for more information.</p></li>
|
||
|
|
|
||
|
|
<li><p>(Optional) <strong><a href="seccsktf.htm">Change the default SSL keystore and truststore files</a></strong>
|
||
|
|
<br>WebSphere Application Server - Express ships with default SSL keystore and truststore files that should not be used in a production environment, although they can be used in test environments. See this topic for more information.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong><a href="seccglen.htm">Enable global security</a></strong>
|
||
|
|
<br>After you have completed configuring your security settings, enable global security</p></li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|
||
|
|
|