RE: Installing certificates into HMC -- MIDRANGE-L

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

Subject: RE: Installing certificates into HMC
From: Rob Berendt <rob@xxxxxxxxx>
Date: Thu, 28 May 2020 21:26:16 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Ok, we had done two CSR's. One from HMCUSSI and one from HMCUSSG (.corp.dekko.com on both). The lan guy sent them off and got a wild card cert for each. Each with a SAN, or Subject Alternative Name, including the HMCUSSI or HMCUSSG name. So I ended up with 2 pairs of those three files.
On each hmc I imported it's respective star_corp_dekko_com.cer and used DigiCertCA2.cer and TrustedRoot.cer as signing certificates.
Working fine.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

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.