IBM WebSphere V5.0 Security - CGISecurity

. Select CSIv2 Outbound Transport.
Disable SSL by selecting TCPIP.
Note: It is possible to enable SSL for inbound connections and disable SSL
for outbound connections. The reverse is also true.
Configuring Server02
In the Administrative Console, Server02 will be configured for incoming requests
to support identity assertion and to accept SSL connections. Configuration for
outgoing requests and connections are not relevant for this scenario. Follow the
steps below to configure Server02:
1. Configure Server02 for incoming connections. Start the Administrative
Console for Server02, then navigate to the Security -> Authentication
Protocol section.
2. Select CSIv2 Outbound Authentication.
a. Enable Basic authentication by selecting Supported.
b. Disable Client Certificate Authentication by selecting Never.
c. Disable Identity Assertion.
3. Select CSIv2 Outbound Transport.
Disable SSL by selecting TCPIP.
Scenario 5: Interoperability with WebSphere Application
Server 4.x
The purpose of this scenario is to show how secure interoperability can take
place between different releases simultaneously while using multiple
authentication protocols (SAS and CSIv2). For a WebSphere V5 server to
communicate with a WebSphere V4 server, the WebSphere V5 server must
support either IBM or BOTH as the protocol choice. By choosing BOTH, that
WebSphere V5 server can also communicate with other WebSphere v5 servers
which support CSI. If the only servers in your security domain are WebSphere
V5, it is recommended to choose CSI as the protocol since this will prevent the
IBM interceptors from loading. However, if there's a chance that any server will
need to communicate with a previous release of WebSphere, select the protocol
choice of BOTH.
Chapter 6. Securing Java clients 119