× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


I am trying to follow this logic.  If the server (DCM) generated the CSR and the registrar signs it and returned the signed certificate, the returned cert should then be OK to import into DCM. It has the public key that matches the private key in DCM.  I can't see anywhere in Jon's process where the keypair gets mismatched which is why your instructions leave me scratching my head.  He is having an external CA sign his certificate so I'm not sure I know where the "Personal Certificate" would come into play as you referenced.

Pete Helgren
GIAC Secure Software Programmer-Java
AWS Certified Cloud Practitioner
Microsoft Certified: Azure Fundamentals
Twitter - Sys_i_Geek IBM_i_Geek

On 5/25/2022 1:23 AM, Markus Neuhold via MIDRANGE-L wrote:

The error indicates that you tried to renewal process with the newly created and signed certificate. With the new CSR signed from the certificate company the only valid option in DCM is to add the cert as additional certificate and then assign it to all the applications in the DCM. If you any Application Server (IBM Webadministration for i) don't forget to replace the cert's in there as well.

The renewal process inside DCM only works if you keep the initial keypair for the certificate. You may check the SKI (subject key identifier) on both certificates.

https://www.ibm.com/support/pages/node/6515666 -> How To Import Personal Certificates Into a Digital Certificate Manager Keystore on the IBM i OS



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2023 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.