Certificates

+

Search Tips   |   Advanced Search

This topic provides information on Secure Sockets Layer certificates.

Use the IBM HTTP Server iKeyman utility to create a CMS key database file and self-signed server certificate.

For IBM HTTP Server, use the native z/OS key management (gskkyman key database) to create a CMS key database file and self-signed server certificate.

Production Web servers must use signed certificates purchased from a Certificate Authority that supports IBM HTTP Server such as VeriSign or Thawte. The default certificate request file name is certreq.arm. The certificate request file is a PKCS 10 file, in Base64-encoded format.

We can use the iKeyman Key Management utility or iKeyman Key Management utility command line interface that is provided with IBM HTTP Server to create self-signed certificates.

We can use the native z/OS key management (gskkyman key database) to create self-signed certificates.

Self-signed certificates are useful for test purposes but should not be used in a production Web server.

For our convenience, IBM HTTP Server includes several default signer certificates. Be aware that these default signer certificates have expiration dates. It is important to verify the expiration dates of all our certificates and manage them appropriately. When we purchase a signed certificate from a CA, they will provide we access to their most recent signer certificates.

---

 

Sub-topics

List of trusted certificate authorities on the IBM HTTP Server

Certificate expiration dates

SSL certificate revocation list

Obtaining certificates