IBM Support

How to Create a Basic Self-Signed Certificate in DCM

Troubleshooting


Problem

Some applications require a simple self-signed certificate to use for encrypting communication. The steps in this document will help you accomplish that.

Resolving The Problem

Some applications require a simple self-signed certificate to use for encrypting communication. The steps in this document will help you accomplish that.

Note:
These steps require that you have already created a local certificate authority (CA) and the *SYSTEM certificate store. If you need to create your own local CA certificate and the *SYSTEM certificate store first, refer to the following documents:

o How to create the *SYSTEM store in DCM: Database 'DCF Technotes (IBM i)', View 'Products', Document 'How to Create the *SYSTEM Store in DCM'
o How to create the Local Certificate Authority (CA) store in DCM: Database 'DCF Technotes (IBM i)', View 'Products', Document 'How to Create the Local Certificate Authority (CA) Store in DCM'

This quick document assumes that you are already in Digital Certificate Manager and logged into the *SYSTEM store, and that a local CA has already been created in Digital Certificate Manager.

The four basic steps to create your own certificate are as follows:

  1. Select the option for creating a Server or Client certificate.
  2. Select Local Certificate Authority as the option to sign the certificate.
  3. Fill in the certificate details.
  4. Assign the certificate to the application(s).


Once these four steps are done, you should have your own self-signed certificate assigned to the application(s) you selected. The details of these steps are explained below:

    • Step 1



      Click Create Certificate and select Server or client certificate, then click Continue:

      image-20190110165228-1
       

    • Step 2



      Verify that Local Certificate Authority is selected and click Continue:

      image-20190110165258-2
       

    • Step 3



      Choose your key size (2048 is the default recommended key size) and fill in the required information. Below is a brief description of each required field and a screen shot of what was used in this example. Once these are filled in, click Continue at the bottom of the page.

      Certificate Authority (CA): Choose the CA that you would like to sign your certificate.

      Key algorithm: Choose either RDA or ECDSA (most common is RSA)

      Key Size: The default key size is 2048.

      Certificate label: This can be whatever you want, mixed case, numbers, letters, hyphens, etc. The ONLY stipulation is that the name you add here MUST be unique (meaning no other certificates on this system can have the same certificate label).

      Organization name: Your business/organization name.

      State or province: Your state/province name. Note that this MUST be 3 characters or more. Two character state abbreviations will not work.

      Country or region: Your country/region. Note that this MUST be 2 characters only. Three characters will not fit.

      Subject Alternative Name: Do not fill this out. It is unnecessary for creating your certificate and has limited function.

      image-20190110165318-3

    • Step 4



      You should receive a message that states Your certificate was created and placed in the certificate store listed below.
      Now you need to select the application (or applications) you want to use this certificate for. Check any of the boxes that apply to your intended use.

      image-20190110165631-5

      You can check the box for whichever application you wish to use the certificate for, this example shows the SMTP client and FTP server.

      image-20190110165649-6

      After you have selected your desired application(s), click Replace at the bottom (Do not select 'Append' unless you are planning to assign an RSA and a ECDSA certificate to the application ID) and your certificate will be assigned. You should receive a message similar to the following:

      image-20190110165834-7

      Click OK, and you are done. Note that most server applications require a restart after a certificate assignment has been changed. Telnet, the Host Servers, and FTP have code that allows them to pick up dynamic certificate changes under certain conditions.

    [{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Component":"Communications-TCP","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"6.1.0;6.1.1;7.1.0;7.2.0;7.3.0","Edition":"","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSC3X7","label":"IBM i 6.1"},"Component":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSC52E","label":"IBM i 7.1"},"Component":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSC5L9","label":"IBM i 7.2"},"Component":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSTS2D","label":"IBM i 7.3"},"Component":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"","label":""}}]

    Historical Number

    677107828

    Document Information

    Modified date:
    18 December 2019

    UID

    nas8N1010321