This topic provides information on Secure Sockets Layer certificates.
For IBM HTTP Server, use the native z/OS® key management (gskkyman key database) to create a CMS key database file and 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.
You can use the IKEYMAN Key Management utility or IKEYMAN Key Management utility command line interface that is provided with IBM HTTP Server to create server certificates.
You can use the native z/OS key management (gskkyman key database) to create server certificates.
Self-signed certificates are useful for test purposes but should not be used in a production Web server.
For your 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 your certificates and manage them appropriately. When you purchase a signed certificate from a CA, they will provide you access to their most recent signer certificates.