IBM WebSphere V5.0 Security - CGISecurity

15.The changes should be saved and WebSphere restarted.
Of course, it is necessary for Global Security to be enabled in order for SSL to
operate; ensure that this is the case.
10.12.3 Configuring the Java client
A J2EE application client environment provides the necessary libraries to
connect via SSL and so no additional effort from the client application developer
is required. Configuration is provided in the sas.client.props file, which is located
in WebSphere’s properties directory by default. For details regarding the options
available in this file, consult 6.3, “Configuring the Java client” on page 103.
Before starting configuration of the Java client, it is recommended that you back
up the current sas.client.props file.
To allow for a secure connection to WebSphere, the following settings are
necessary.
Table 10-4 sas.client.props configuration
Property
com.ibm.CORBA.securityEnabled
com.ibm.ssl.protocol
com.ibm.CSI.performTransportAssocSSLTLSSupported
com.ibm.CSI.performTransportAssocSSLTLSRequired
com.ibm.CSI.performMessageIntegritySupported
com.ibm.CSI.performMessageConfidentialitySupported
Value
true
SSL
true
true
true
true
Once the sas.client.props file has been updated, it should be saved to the
filesystem.
Testing the configuration involves starting a Java client with the launchclient tool.
Information regarding the launchclient tool can be found in 6.5, “J2EE application
client” on page 121.
Additionally, the client must provide a certificate in order to establish its identity,
rather than a user name and password. Java clients can be configured to provide
a certificate and in this case, several additional steps are necessary.
The sas.client.props file must be updated to reflect the addition of the client trust
store.
Chapter 10. Administering WebSphere security 315