IBM WebSphere V5.0 Security - CGISecurity

Configuring Client01Client01 requires message layer authentication with an SSL transport; follow thesteps to configure Client01.1. The client needs to point to the sas.client.props file using the property in thecommand line, see 6.3, “Configuring the Java client” on page 103 for moreinformation on this; you can use the following parameter:com.ibm.CORBA.ConfigURL=file:/c:/websphere/appclient/properties/sas.client.props.2. All further configuration involves setting properties within the sas.client.propsfile, open it in a text editor at the /propertiesdirectory.3. Enable SSL for the connection; in this case, SSL will be supported but notrequired: com.ibm.CSI.performTransportAssocSSLTLSSupported=true,com.ibm.CSI.performTransportAssocSSLTLSRequired=false.Enable client authentication at the message layer. In this case, clientauthentication is supported but not required:com.ibm.CSI.performClientAuthenticationRequired=falsecom.ibm.CSI.performClientAuthenticationSupported=true4. Use all of the rest of the defaults in the sas.client.props file. Save the file thenclose it.Configuring Server01In the Web Console, Server01 will be configured for incoming requests tosupport message layer client authentication and incoming connections to supportSSL without client certificate authentication. Server01 will be configured foroutgoing requests to support identity assertion. Follow the steps to configureServer01:1. Configure Server01 for incoming connections. Start the AdministrativeConsole for Server01, then navigate to the Security -> AuthenticationProtocol section.a. Select CSIv2 Inbound Authentication.i. Enable Basic Authentication, by selecting Supported.ii. Disable Client Certificate Authentication by selecting Never.iii. Disable Identity Assertion.b. Select CSIv2 Inbound Transport.Enable SSL, by selecting SSL-Supported.Chapter 6. Securing Java clients 111