Administrator Launcher does not work if we define a http context path about connect HOT 6 CLOSED

Created an issue for this: MIRTH-4380

from connect.

@davutg Your issue doesn't seem related to this but I'll comment here before closing this issue. It sounds like you are building Connect on your own, self signing the jars, and using the Admin Launcher to load the Connect Client. The Admin Launcher is built with your security in mind and to ensure the jars are signed properly by a known good entity. If you are indeed building Connect on your own then you should sign your jars with one of the "official" Java JCE code signing CA certs (CN=JCE Code Signing CA).

The other option, though it is only recommended for use while developing and not in production, is to launch the Admin Launcher with the -k option which:

"Allows JARs signed with self-signed certificates to be verified. This should only be used for development/testing purposes."

If these assumptions aren't correct then I suggest you open a new issue that is specific to the problem you are experiencing.

from connect.

Thanks ! :)

from connect.

Trust anchor for certification path not found.

Even for https://localhost:8443 for current 3.9.0 dev branch with Admin Launcher 1.1.0.

-JDK 1.8 update 20
-Site address is added in Control Panel Java secure sites and security option High selected.
-SSL is added to Trusted Root Authorities (confirmed after registering to physical registry).

After uninstalling administrative console I'm able to start MirthUI thru JNLP.

I'm not able to figure out exactly since I don't have access to Admin Launcher but it appeared to me mirthconnect alias certificate is not signed from CA Auths and Admin Launcher is trying to validate it but it fails on its own Trust Manager for some reason. Maybe it's SSLContext is different.

from connect.

Closing, issue is fixed in Admin Launcher 1.1.0 release.

from connect.

@cturczynskyj Thanks , really appreciated your explanation. I compile myself, because I coded https SSL certificate support and UDP support kind of things in addition to this open source edition. Yes, our certificate is self signed and I don't know how to let admin launcher to let it work. It's also okay without launcher for us, but happy to see that this issue is resolved.

from connect.