IBM WebSphere V5.0 Security - CGISecurity

Configuring Server02
All previous releases of WebSphere Application Server only support the SAS
authentication protocol. There are no special configuration steps needed other
than enabling global security on server (Server02).
Configuring Server03
In the Administrative console, Server03 will be configured for incoming requests
to message layer authentication and to accept SSL connections. Configuration
for outgoing requests and connections are not relevant for this scenario. follow
the steps below to configure Server03.
1. Configure Server03 for outgoing connections. Start the Administrative
Console for Server03, then navigate to the Security -> Authentication
Protocol section.
2. Select Global Security.
Select CSI and SAS or CSI for active protocol.
3. Select CSIv2 Outbound Authentication.
a. Disable Basic Authentication by selecting Never.
b. Disable Client Certificate Authentication by selecting Never.
c. Enable Identity Assertion.
4. Select CSIv2 Outbound Transport.
Enable SSL by selecting SSL-Supported.
Note: If Server03 is only communicating with WebSphere Application Server
Version 5.0 servers, it is recommended that you choose the CSI protocol.
Otherwise, choose a protocol of BOTH.
6.5 J2EE application client
A J2EE application client operates in a similar fashion to a J2EE server-based
application and has access to some of the J2EE APIs. The application client will
perform a JNDI lookup to retrieve a home interface as per usual J2EE
programming practices. The process for developing and assembling a J2EE
application client is documented in the InfoCenter.
Chapter 6. Securing Java clients 121