× 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.



This page has several FAQ about DCM.

http://www-01.ibm.com/support/docview.wss?uid=nas8N1010356


Chris Bipes
Director of Information Services
CrossCheck, Inc.


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Tuesday, August 01, 2017 9:46 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: SSL Certificate format

Ever since we first started putting SSL certificates on our system we have use Verisign. Process was simple. We got the certificate from Verisign, we put it in the IFS, we loaded it into DCM and applied it to servers/services. We are now for the first time using a Comodo certificate and the Comodo site is asking what format we want the certificate file in. In the past with Verisign that was never asked and I think we just told Verisign that we used an IBM i and we got the correct certificate. The only reference I can find to the format that DCM wants to use is an obscure reference to X.509. Can anyone confirm that X.509 is the format of the certificate we want to get from Comodo? It is listed as a format but there are also 6 other formats listed and our security expert (Windows and Cisco) also said that there are tools to convert certificates to additional formats. I see file formats for .pem, .crt, .ca-bundle, cer, p7b, p7s, pfx. Never realized there were so many. We have
also received .cer files from Verisgn but that is not an option on the Comodo site.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2024 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.