13.07.2015 Views

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Figure 10-18 J2C Authentication entry in the Administrative Console4. Save the configuration.The J2C Authentication Entries are stored in the security.xml file under the\config\cells\ directory. The password fields areencoded in the file.For more information on J2C security, refer to 7.3, “J2C security” on page 169.10.8 Configuring SSLThe SSL implementation used by the application server is the <strong>IBM</strong> Java SecureSockets Extension (JSSE). The JSSE is a set of Java packages that enablesecure Internet communications. It implements a Java version of the SSL andTLS protocols and includes functionality for data encryption, serverauthentication, message integrity and client authentication. Configuring JSSE isvery 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 keyfile, but it also allows a separate file, called a trust file, to be specified. A trustfile can contain only signer certificates. Therefore, all personal certificates canbe 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 bythe plug-in (.kdb files); instead, it recognizes standard file formats such asJKS (Java Key Store). As such, SSL key files cannot be shared between the258 <strong>IBM</strong> <strong>WebSphere</strong> <strong>V5.0</strong> <strong>Security</strong> Handbook

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!