Scenario 5: Interoperability with WAS Version
The purpose of this scenario is to show how secure interoperability can occur between different releases simultaneously while using multiple authentication protocols (Security Authentication Service (SAS) and CSIv2). For WAS v5 to communicate with a WAS Version 4, Version 5 server must support either IBM or BOTH as the protocol choice. By choosing BOTH, the Version 5 server also can communicate with other Version 5 servers that support CSI. If the only servers in your security domain are version 5, it is recommended that you choose CSI as the protocol because this prevents the IBM interceptors from loading. However, a chance exists that any server has to communicate with a previous release of WAS, select the protocol choice of BOTH.
Configuring the S1 server
The S1 server requires message layer authentication with an SSL transport. The protocol for the S1 server must be BOTH. Configuration for incoming requests for the S1 server is not relevant for this scenario. To configure the S1 server for outgoing connections...
- Disable identity assertion.
- Enable user ID and password authentication.
- Enable SSL.
- Disable SSL client certificate authentication.
- Set authentication protocol to BOTH in the global security settings.
Configuring the S2 server
All previous releases of WAS support the SAS authentication protocol only. No special configuration steps are needed other than enabling global security on the server (S2).
Configuring the S3 server
In the administrative console, the S3 server is 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.
- Enable identity assertion.
- Disable user ID and password authentication.
- Enable SSL.
- Disable SSL client authentication.
- Set authentication protocol to either CSI or BOTH.
See AlsoScenario 1: Basic authentication and identity assertion
Scenario 2: Basic authentication, identity assertion and client certificates
Scenario 3: Client certificate authentication and RunAs system
Scenario 4: TCP/IP transport using a Virtual Private Network