Example 2: Set basic authentication, identity assertion, and client certificates
This example is the same as example 1, except for the interaction from client C2 to server S2. Therefore, the configuration of example 1 still is valid, but we have to modify server S2 slightly and add a configuration for client C2. The configuration is not modified for C1 or S1.
- Set client C2 for transport layer authentication (SSL client certificates).
- Point the client to sas.client.props.
Use the com.ibm.CORBA.ConfigURL=file:/C:/was/properties/sas.client.props property. All further configuration involves setting properties within this file.
- Enable SSL. In this case, SSL is supported but not required:
- Disable client authentication at the message layer.
- Enable client authentication at the transport layer where it is supported, but not required.
- Set the server, S2.
In the admin console, server S2 is configured for incoming requests to SSL client authentication and identity assertion. Configuration for outgoing requests is not relevant for this example. We can mix and match these configuration options. However, a precedence exists as to which authentication features become the identity in the received credential:
- Identity assertion
- Message-layer client authentication (basic authentication or token)
- Transport-layer client authentication (SSL certificates)
- Enable identity assertion.
- Disable user ID and password authentication.
- Enable SSL.
- Enable SSL client authentication.
Set CSIV2 inbound and outbound communication settings
Example 1: Set basic authentication and identity assertion
Example 3: Set client certificate authentication and RunAs system
Example 4: Set TCP/IP transport using a virtual private network