IBM WebSphere V5.0 Security - CGISecurity

►
►
Client certificate label: ClientKey
Client trust file: ClientTrustFile.jks
Exchange the certificates between the two parties, export the ServerKey from
the ServerKeyFile.jks and import it into the ClientTrustFile.jks; export the
ClientKey from the ClientKeyFile.jks and import it into the ServerTrustFile.jks.
10.12.2 Server side configuration
The Application Server must be configured to support SSL. An SSL configuration
should exist that describes the type of key stores used to establish the secure
connection and their location. Refer to 10.9.4, “Configuring WebSphere to use a
key store” on page 276 for details on key stores.
Note: The sas.server.props configuration file used in WebSphere Application
Server, version 4 is no longer used in version 5. However, the file remains in
the properties directory. The server security configuration is contained in a file
called security.xml whose default location is
/config/cells/BaseApplicationServerCell.
Create a new SSL entry in the SSL Repertoire, following the steps in 10.8.1,
“SSL configurations” on page 259 and using the following values for the
attributes:
►
►
►
►
►
SSL alias: ORB SSL
Key file: C:\WebSphere\Appserver\etc\ServerKeyFile.jks
Key file password: password
Trust file: C:\WebSphere\Appserver\etc\ServerTrustFile.jks
Trust file password: password
The authentication protocol must be configured to use the correct SSL settings.
1. Log in to the WebSphere Admin console, select Security -> Authentication
Protocol -> CSIv2 Inbound Authentication.
2. Ensure that Basic Authentication is supported, at the very least. It is also valid
to set Basic Authentication to Required.
Note: When required is set to true for an attribute, where supported is also an
option, the supported attribute will not be used by the server.
This is true for every attribute within CSI also.
Chapter 10. Administering WebSphere security 311