BEA WebLogic Server 10.0 Security Schema Reference

http://www.bea.com/ns/weblogic/920/domain
element security-context-enabled

Model
<security-context-enabled>boolean</security-context-enabled>
Disallowed substitutions (block)
none (extensions, restrictions and substitutions are allowed)
Substitution group exclusion (final)
none (extensions and restrictions are allowed)
Usage
Documentation
<p>Indicates whether this Jolt connection pool passes the
 connection pool's security context (user name, password and other
 information) from the WebLogic Server user to the Tuxedo
 domain.</p>

 <p>If you enable the connection pool to pass the security context,
 you must start the Jolt Service Handler (JSH) with the
 <code>-a</code> option. When the JSH gets a message with the
 caller's identity, it calls <code>impersonate_user()</code> to get
 the appkey for the user. JSH caches the appkey, so the next time
 the caller makes a request, the appkey is retrieved from the cache
 and the request is forwarded to the service. A cache is maintained
 by each JSH, which means that there will be a cache maintained for
 all the session pools connected to the same JSH.</p>

 <p>You must enable Security Context if Tuxedo requires secured
 connections.</p>
 (Interface=weblogic.management.configuration.JoltConnectionPoolMBean Attribute=isSecurityContextEnabled)
Fundamental Facets
equality, non-numeric, unbounded, unordered, finit value space
White Space Processing
collapse
BEA WebLogic Server 10.0 Security Schema Reference

Version: 10.0