InfoCenter Home > 5.5.6.2.5: Making client and server keyrings accessibleAfter you have created keyring classes and inserted the necessary certificates, you need to make the keyring classes accessible to the client and server programs. To use created server and client keyrings in your WebSphere environment, you must first copy them to the client and server machines.
Managing the Server SSL Keyring FilesThe administrative model in WebSphere Application Server allows the SSL settings for each WebSphere component to be centrally and individually managed. SSL settings are centrally managed in the administrative console through the default SSL Settings panel. In addition, any of the default settings can be overridden for an individual component by using the HTTPS, ORB, and LDAPS SSL settings panels. See article 6.6.18, Securing applications, for more detailed information about using the administrative console to configure WebSphere security.
The Default SSL Settings panel can be used to configure WebSphere Application Server components using SSL. Parameters that are set through the ORB SSL Settings panel override the default SSL settings for the ORB. Regardless of which settings are in effect, the ORB uses these settings as follows. (Additionally, the ORB requires the SAS properties files on the client and server to be configured as described below.)
Managing the Client SSL Keyring FilesYou need to modify the sas.client.props file, which is located in the product installation root/properties directory. If you used "WebAS" as the password when you generated the client and server keyrings, you need to make the following changes to the sas.client.props file:
You can now start your WebSphere application using the newly created keyring classes. |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|