We are getting crap from providers now that having an HMC with a self
signed certificate is no longer acceptable. Such a device may be banned
from their equipment racks and it now violates various requirements.
It's not just the HMC of course it's IBM i, switches, firewalls,
routers, SANs, tape libraries, and the beat goes on.
Obtaining a separate key for every device in the DC is both expensive
and a management nightmare.
So a wildcard it is. Working in many places but from IBM: "the hmc does
not support adding a wildcard certificate."
There is a POSSIBLE workaround that involves creating a java keystore in
jks or pkcs12 format, importing the wildcard to that and then importing
that keystore into the HMC.
Has anyone experience with creating a Java Keystore that might have
insights into doing that? 'The Google' returns thousands of hits but
they all seem to think I'm a java expert to start with.
Anyone put a wildcard cert into their HMC??
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.
midrange.com
