I tried searching for this, hopefully I haven't missed something obvious.
The keystore.jks file in appdata thata comes with the installed instance of mirth connect contains a self signed certificate. I was looking to replace this with a certificate from our internal CA. I was able to create a new keystore.jks with a new mirthconnect key pair that was signed by our internal CA.
I am able to go to the web portal and the key is correct etc. However, launching the java utility no longer works, it states that it is unable to contact the instance. Switch it back to the original keystore, everything works fine.
I have installed our CA in Windows as well as importing the CA chain into Java, however it still won't launch. Anyone know what I am missing?
This is on mirth connect 3.2.1 running on Oracle Java 8 hosted on a RHEL 7 system. Client is a Windows 8 system running Oracle Java 8.
-Erinn
The keystore.jks file in appdata thata comes with the installed instance of mirth connect contains a self signed certificate. I was looking to replace this with a certificate from our internal CA. I was able to create a new keystore.jks with a new mirthconnect key pair that was signed by our internal CA.
I am able to go to the web portal and the key is correct etc. However, launching the java utility no longer works, it states that it is unable to contact the instance. Switch it back to the original keystore, everything works fine.
I have installed our CA in Windows as well as importing the CA chain into Java, however it still won't launch. Anyone know what I am missing?
This is on mirth connect 3.2.1 running on Oracle Java 8 hosted on a RHEL 7 system. Client is a Windows 8 system running Oracle Java 8.
-Erinn
Replacing SSL/TLS certificates
0 commentaires:
Enregistrer un commentaire