IBM Support

Method for Importing a Renewed Certificate without Generating a CSR

Troubleshooting


Problem

This document goes through the steps needed to import a renewed certificate signed by an Internet CA without a CSR.

Resolving The Problem

NOTE: For instruction on how to accomplish this task using the updated Digital Certificate Manager for i interface ('http://systemName:2001/dcm' or 'https://systemName:2010/dcm'), see the following documentation:

When attempting to use the Manage Certificates > Import Certificate function and specifying *SYSTEM along with Server or client, it is failing with a message about a missing CSR, which was not generated for this renewal.

To resolve the problem, do the following:
1. Using your browser, sign on the ADMIN instance to get to the TASKS page.
2. Click on Digital Certificate Manager. (DCM)
3. Click on Select a Certificate Store.
4. Select *SYSTEM.
5. Type the password.
6. Click the triangle next to FastPath.
7. Click on Work with Server and Client Certificates.
8. Click the bullet next to the certificate that is soon to expire.
9. Click the Renew button.
10. Click the bullet next to Verisign, and click Continue.
11. Click the bullet next to No - Import the renewed signed certificate from an existing file, and click Continue.
Note: DCM requires that any automatic certificate renewal be issued by the same CA certificate that issued the original server certificate.
12. Type the full Integrated File System /path/filename.extension of your renewal, and click Continue.
13. This will result in a new server certificate. Assign it to applications, and cycle the applications. You will be up and running with the new certificate.

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CISAA2","label":"Digital Certificate Manager"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.2.0;7.3.0;7.4.0;7.5.0"}]

Historical Number

410816678

Document Information

Modified date:
27 October 2022

UID

nas8N1015025