IBM WebSphere V5.0 Security - CGISecurity

Figure 10-18 J2C Authentication entry in the Administrative Console
4. Save the configuration.
The J2C Authentication Entries are stored in the security.xml file under the
\config\cells\ directory. The password fields are
encoded in the file.
For more information on J2C security, refer to 7.3, “J2C security” on page 169.
10.8 Configuring SSL
The SSL implementation used by the application server is the IBM Java Secure
Sockets Extension (JSSE). The JSSE is a set of Java packages that enable
secure Internet communications. It implements a Java version of the SSL and
TLS protocols and includes functionality for data encryption, server
authentication, message integrity and client authentication. Configuring JSSE is
very similar to configuring most other SSL implementations (for example, GSKit);
however, a few differences are worth noting.
►
►
JSSE allows both signer and personal certificates to be stored in an SSL key
file, but it also allows a separate file, called a trust file, to be specified. A trust
file can contain only signer certificates. Therefore, all personal certificates can
be stored in an SSL key file and all signer certificates stored in a trust file.
JSSE does not recognize the proprietary SSL key file format that is used by
the plug-in (.kdb files); instead, it recognizes standard file formats such as
JKS (Java Key Store). As such, SSL key files cannot be shared between the
258 IBM WebSphere V5.0 Security Handbook