MeshCommander is a Intel(R) Active Management Technology (Intel(R) AMT) remote management tool. It's feature rich and includes a built-in remote desktop viewer for Hardware-KVM, a Serial-over-LAN terminal, IDER-Redirection support and much more. MeshCommander is built on web technologies and runs on many plaforms. In addition to being available as a stand-alone tool, MeshCommander was built to be very space efficient to that it can be uploaded into Intel AMT flash space to have it served diretly from the Intel AMT web serve.
I created a pfx with openssl that I imported into MeshCommander. If I open that certificate in Windows, I can see a valid certification path. Now I connect to AMT and issue a cert with that same certificate. If I view the certificate properties, the common name of the issuing certificate matches the pfx. But if I download the certificate and open in WIndows, the certification path is broken: "The issuer of this certificate could not be found."
If I begin with a root cert generated in MeshCommander, the certification path is not broken.
The Root CA generated by MeshCommander and the PFX certificate are both 2048bit Sha256RSA
I created a pfx with openssl that I imported into MeshCommander. If I open that certificate in Windows, I can see a valid certification path. Now I connect to AMT and issue a cert with that same certificate. If I view the certificate properties, the common name of the issuing certificate matches the pfx. But if I download the certificate and open in WIndows, the certification path is broken: "The issuer of this certificate could not be found."
If I begin with a root cert generated in MeshCommander, the certification path is not broken.
The Root CA generated by MeshCommander and the PFX certificate are both 2048bit Sha256RSA
Please help!