25 lines
1.4 KiB
HTML
25 lines
1.4 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>Simple WebSphere Authentication Mechanism</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h5><a name="secswam"></a>Simple WebSphere Authentication Mechanism</h5>
|
||
|
|
|
||
|
|
<p>The SWAM authentication mechanism is intended for simple, non-distributed, single application server runtime environments. The single application server restriction is due to the fact that SWAM does not support forwardable credentials. This means that if an object in one application server process invokes a method on an object that resides in a second process, the identity of the caller in the first process is not transmitted to the second process. What is transmitted is an unauthenticated credential, which, depending on the security permissions configured on the methods, may cause authorization failures.</p>
|
||
|
|
|
||
|
|
<p>Because SWAM is intended for a single application server process, single-sign-on (SSO) is not supported.</p>
|
||
|
|
|
||
|
|
<p>The SWAM authentication mechanism is suitable for simple environments, software development environments, or other environments that do not require a distributed security solution.</p>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|
||
|
|
|