IBM WebSphere V5.0 Security - CGISecurity

Table 10-7 IBM SAS-specific sas.client.props configuration
Property
com.ibm.ssl.sas.outbound.keyStore
com.ibm.ssl.sas.outbound.keyStorePassword
com.ibm.ssl.sas.outbound.keyStoreType
com.ibm.ssl.sas.outbound.trustStore
com.ibm.ssl.sas.outbound.trustStorePassword
com.ibm.ssl.sas.outbound.trustStoreType
com.ibm.ssl.sas.outbound.protocol
Value
JKS
JKS
SSLv3
Once SSL is configured, use the launchclient tool provided with WebSphere to
test the connection. It may be feasible to run a packet monitoring tool to be sure
that the information passing from client to server is, in fact, encrypted. Only the
server and client certificates should be sent in the clear and then only during the
initialization stage. In any case, these certificates are considered to be viewable
by the public in general as they do not contain any private information.
Should an error occur, the likelihood is that a Java exception trace will appear in
the client console. Often the errors refer to CORBA problems, CORBA being the
underlying marshalling mechanism with which the ORBs operate. Most CORBA
exceptions are difficult to interpret due to their somewhat terse messages.
Tracing can also provide a useful insight to the events that led up to the error.
10.13 Connecting to directory servers (LDAP)
This section will discuss the LDAP User Registry configuration for the
WebSphere Application Server. The user registry we used to show the
configuration steps is the IBM SecureWay Directory Server V3.2.2. This section
will show you how to configure your LDAP server for this sample, and how to
create a sample user and a sample group entry in the directory. We provide an
example of how to configure WebSphere to use a given LDAP server over a
normal LDAP connection, then use SSL for LDAP (LDAPS).
For other LDAP servers, refer to Appendix B, “LDAP configurations” on
page 461.
Chapter 10. Administering WebSphere security 317