Using IBM Certificate Management for HATS applications
Certificate Management allows you to create and manage certificates required for Secure Sockets Layer
(SSL) connections.
For HATS, SSL is used between the following:
- A HATS application and the Telnet server for secure connections
- The Digital Certificate Access Server (DCAS) and client for Web Express Logon (WEL) in a HATS
application to retrieve host credentials.
Certificate Management topics
Creating a key database file
Using a well-known, trusted Certificate Authority
Creating the certificate request
Sending the certificate request
Storing the certificate
Using an unknown Certificate Authority
Creating the certificate request
Sending the certificate request
Storing the certificate
Using a self-signed certificate
Exchanging certificates
Before you begin configuring SSL for HATS applications, you must create a key database file.
Some applications might use the terminology of keystore file or truststore file.
To create a new key database file:
- Click Start > Programs > IBM WebSphere HATS > Certificate Management.
- Click Key Database File > New.
- Select PKCS12, JKS, or JCEKS key database file for the key database type.
Note: PKCS12 is required for secure connections between HATS applications and the Telnet server.
- Type a file name. HATS does not require a particular file name.
- Type a directory name for the Location. HATS does not require a particular directory for creation
of the key database file, but the key database file will need to be copied into an
Enterprise Archive file (.ear) in order to deploy an application that uses it.
- Click OK.
- Enter a new password.
- Enter the same password again to verify.
-
To help ensure adequate security, the password should have an expiration date.
To set expiration date for the password,
click Set expire time and specify the number of days until the password expires.
- Click OK.
To open an existing key database file:
- Click Key Database File > Open.
- Change to the directory containing the key database file.
- Type the key database file name and click Open.
- Enter the current password and click OK.
After you have created or opened the key database file, you can:
- Request a certificate from a predefined well known certificate authority (CA).
This procedure requires less configuration. The key database files are preconfigured with the CA root
certificates required to identify the CAs from whom the server certificate is issued.
- Request a certificate from an unknown certificate authority.
This procedure requires more configuration. You must also obtain and store the server certificate issued
by the CA and the CA's root certificate in the key database file.
In addition, you must make the root certificate available to the SSL partners from which you want to
obtain host credentials.
- Create a self-signed certificate.
This procedure does not require a certificate authority and can be used immediately after installing the
server. However, the self-signed certificate must be made available to the SSL partners.
This procedure can also be used for testing until a certificate is obtained from a certificate authority.
- Exchange certificates with SSL partners.
In some configurations, certificates in the server's key database file
must be made available to any SSL partners, such as the Telnet or DCAS server, to enable SSL communications.
Note: Whenever you change the key database file used by a running HATS application,
you must stop and re-start the HATS application.
Complete the procedures in this section to set up SSL security using a
certificate issued by a well-known Certificate Authority (CA).
The following CA signer certificates are automatically stored
in a newly created key database file and marked as trusted certificates:
- Thawte Personal Premium CA
- Thawte Personal Freemail CA
- Thawte Personal Basic CA
- Thawte Premium Server CA
- Thawte Server CA
- RSA secure server CA (also obtained from VeriSign)
- VeriSign class 4 public primary CA
- VeriSign class 3 public primary CA
- VeriSign class 2 public primary CA
Following is an overview of the steps used to set up
SSL security using a well-known CA:
To create the public/private keys and certificate request:
- On the Certificate Management window,
choose Personal Certificate Requests from the drop-down list then click New.
- Enter the name (label) that is used to identify the key and certificate
within the database.
- Enter the number corresponding to the key size you want to use.
Choosing a larger key size results in stronger security, but requires more processing
on the client and the server to establish a connection.
- Enter the TCP/IP host name of the server that owns the certificate as the common name, for
example, canes10.raleigh.ibm.com.
- Enter an organization name.
- Optionally enter an organization unit, and other location information.
- Choose a country code.
- Enter a certificate request file name, or use the default file name.
When you click OK, your information is processed and several files will
be produced or updated in the directory where you created the certificate request.
If you backup your key database, backup these files also.
Do not attempt to edit these files, as the key database file or the certificate request can be corrupted.
Start a Web browser and access the certificate authority's (CA) Web page.
Follow the instructions provided to submit the certificate request.
The following list provides the URLs of some well-known CAs:
- VeriSign:
http://www.verisign.com/
- Thawte:
http://www.thawte.com/
Depending on the CA you choose, you can either e-mail the certificate
request generated by Certificate Management or incorporate the certificate request into the
form or file provided by the CA.
While you are waiting for the CA to process your certificate request, you
can enable SSL security for testing by creating and storing a self-signed certificate using the procedure
described in
Using a Self-Signed Certificate.
When you receive the certificate from the CA, use Certificate Management to put the
certificate into the key database file.
You should make a backup copy of the received certificate before starting this step.
- Choose Personal Certificates from the drop-down list then click Receive
to receive the certificate request.
The Receive Certificate from a File window appears.
- The data type must be BASE64 encoded ASCII data (armored 64 format).
- Enter the certificate file name.
- Enter the location (path name) of the certificate.
- Click OK.
The certificate you just stored is displayed as the first item.
- Highlight the certificate you just stored and click View/Edit.
The Key information window appears.
- If not already checked, click Set the certificate as the default
to set the selected key as the default.
- The certificate name should appear under the Personal Certificate
drop-down list and the certificate request should disappear from under
the Personal Certificate Requests drop-down list.
- Copy the key database file to the Enterprise Archive
for deployment. If the Enterprise Archive is running, stop and re-start it.
Complete the procedures in this section to set up SSL security using a
certificate issued by a Certificate Authority (CA) that is not already defined in the database.
Following is an overview of the steps used to set up SSL security using a certificate
from a CA that is not predefined:
To create the public/private keys and certificate request:
- On the Certificate Management window,
choose Personal Certificate Requests from the drop-down list then click New.
- Enter the name (label) that is used to identify the key and certificate
within the database.
- Enter the number corresponding to the key size you want to use.
Choosing a larger key size results in stronger security, but requires more processing
on the client and the server to establish a connection.
- Enter the TCP/IP host name of the server that owns the certificate as the common name, for
example, canes10.raleigh.ibm.com.
- Enter an organization name.
- Optionally enter an organization unit, and other location information.
- Choose a country code.
- Enter a certificate request file name, or use the default file name.
When you click OK, your information is processed and several files will
be produced or updated in the directory where you created the certificate request.
If you backup your key database, backup these files also.
Do not attempt to edit these files, as the key database file or the certificate request can be corrupted.
Follow the unknown CA's procedures to submit the certificate request.
Depending on the CA you choose, you can either e-mail the certificate
request generated by Cerficate Management or incorporate the certificate request into the
form or file provided by the CA.
While you are waiting for the CA to process your certificate request, you
can enable SSL security for testing by creating and storing a self-signed certificate using the procedure
described in
Using a Self-Signed Certificate.
When you receive the certificate from the CA,
contact the CA to obtain the CA's root certificate.
You must store the CA root certificate in the key database file
before you store the applied-for certificate.
The CA root certificate is used to validate the applied-for certificate.
You should make a backup copy of both the CA's root certificate as well
as the certificate issued to your server before starting this step.
To store the CA's root certificate:
- Choose Signer Certificates from the drop-down list then click Add
to receive the CA root certificate.
- The data type must be BASE64 encoded ASCII data (armored 64 format).
- Enter the certificate file name.
- Enter the location, or path, of the certificate.
- Click OK.
The file is marked as "trusted" and is stored.
To store the applied-for certificate:
- Choose Personal Certificates from the drop-down list then click Receive
to receive the applied-for certificate.
- The data type must be BASE64 encoded ASCII data (armored 64 format).
- Enter the certificate file name.
- Enter the location, or path, of the certificate.
- Click OK.
The certificate you just stored is displayed as the first item.
- Highlight the certificate you just stored and click View/Edit.
The Key information window appears.
- If not already checked, click Set the certificate as the default
to set the selected key as the default.
- The certificate name should appear under the Personal Certificate
drop-down list and the certificate request should disappear from under
the Personal Certificate Requests drop-down list.
- Copy the key database file to the Enterprise Archive (.ear)
for deployment. If the Enterprise Archive is running, stop and re-start it.
Use the following procedures to create and use a self-signed certificate:
- Choose Personal Certificates from the drop-down list.
- Click Create > New Self-signed Certificate.
- Enter the name (label) that is used to identify the key and certificate
within the database.
- Select X509 V3 as the certificate version.
- Enter the number corresponding to the key size you want to use.
Choosing a larger key size results in stronger security, but requires more processing
to establish a connection.
- Enter the TCP/IP host name of the server that owns the certificate as the common name, for
example, canes10.raleigh.ibm.com.
- Enter an organization name.
- Optionally enter an organization unit, and other location information.
- Choose a country code.
- Enter the number of days the self-signed certificate is to be valid.
- Highlight the certificate you just created and click View/Edit.
The Key information window appears.
- If not already checked, click Set the certificate as the default
to set the selected key as the default.
- Click OK.
- Copy the key database file to the Enterprise Archive (.ear)
for deployment. If the Enterprise Archive is running, stop and re-start it.
In some configurations, certificates must also be made available to SSL partners, for example the DCAS
server.
If your server uses a certificate from an unknown CA, the unknown CA's root certificate must be made
available to SSL partners.
If your server uses a self-signed certificate, a copy of the self-signed certificate must be made
available to SSL partners.
To create a certificate file to exchange:
- Open the key database file using Certificate Management.
- If your server uses a self-signed certificate:
- Display the list of personal certificates.
- Highlight the certificate used by your server.
- Click Extract Certificate.
If your server uses a certificate issued by an unknown CA:
- Display the list of Signer Certificates.
- Highlight the root certificate of the CA that issued
the certificate for your server.
- Click Extract.
- On the Extract Certificate to a File window, choose either
Base64 encoded ASCII data or Binary DER data.
Base64 is usually used if the certificate will be securely transferred
through e-mail.
The certificate file name and location can be any you choose.
- Click OK and the certificate file will be created.
- Securely transfer the certificate file to the SSL partner, for example the DCAS
server, and add the certificate to the its key database file.