49 lines
2.8 KiB
HTML
49 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>Tune your security configuration</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h2><a name="sectune"></a>Tune your security configuration</h2>
|
||
|
|
|
||
|
|
<p>Performance issues typically involve trade-offs between function and speed. Usually, the more function and the more processing involved, the slower the performance will be. Consider what type of security is necessary and what you can disable in your environment. For example, if your application servers are running in a Virtual Private Network (VPN), consider whether you must disable Single Sockets Layer (SSL). If you have a lot of users, can they be mapped to groups and associated the groups to your J2EE roles? These questions are things to consider when designing your security infrastructure.</p>
|
||
|
|
|
||
|
|
<p>There is always a trade-off between performance, feature and security. Security typically adds more processing time to your requests, but for a good reason. Not all security features are required in your environment. When you decide on tuning security, you should create a benchmark before making any change to ensure the change is improving performance.</p>
|
||
|
|
|
||
|
|
<p>In a large scale deployment, performance is very important. Running benchmark measurements with different combinations of features can help you to determine the best performance versus benefit configuration for your environment.</p>
|
||
|
|
|
||
|
|
<p>See these topics for more information about how you can tune your WebSphere security configuration:</p>
|
||
|
|
|
||
|
|
<blockquote>
|
||
|
|
<p><strong><a href="sectugen.htm">General security tuning tips</a></strong>
|
||
|
|
<br>See this topic for tips that can improve the general performance of WebSphere security.</p>
|
||
|
|
|
||
|
|
<p><strong><a href="sectucsi.htm">Tune CSIv2</a></strong>
|
||
|
|
<br>If you are using the Common Security Interoperability Version 2 (CSIv2) authentication protocol, this topic offers considerations that can tune your configuration.</p>
|
||
|
|
|
||
|
|
<p><strong><a href="sectuldp.htm">Tune LDAP authentication</a></strong>
|
||
|
|
<br>If you are using an LDAP user registry, see this topic for pointers to optimize the authentcation process.</p>
|
||
|
|
|
||
|
|
<p><strong><a href="sectuweb.htm">Tune Web authentication</a></strong>
|
||
|
|
<br>If you are using browser-based authentication, see this topic for tuning tips.</p>
|
||
|
|
|
||
|
|
<p><strong><a href="sectuaut.htm">Tune authorization</a></strong>
|
||
|
|
<br>See this topic for ways to speed up the authorization process.</p>
|
||
|
|
|
||
|
|
<p><strong><a href="sectussl.htm">SSL performance tips</a></strong>
|
||
|
|
<br>If you are using SSL connections with WebSphere Application Server, see this topic for tips to improve performance.</p>
|
||
|
|
</blockquote>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|
||
|
|
|