nextgenhealthcare
[BUG] Mirth Connect Administrator Launcher uses connection URL from JNLP instead of user
When using MCAL with a server behind some network shenanigans, the JNLP returned by the server is not correct with respect to the client's view of the server on the network.
For example, let's say you are using an SSH tunnel to connect to your Mirth server:
$ ssh -L8444:localhost:8443 [email protected]
If you then use https://localhost:8444 as the "Address" for your Mirth connection in MCAL, MCAL will connect just fine but then the login window will have https://localhost:8443 (note the port 8443 instead of 8444) in the "Server" box.
That Server box is filled-in from the 3rd command-line argument to com.mirth.connect.client.ui.Mirth's main method. Since MCAL knows the correct client's network name for the MCA address/server, it should use that instead of whatever comes back from the JNLP request.
Same issue if you're using AWS Systems Session Manager and port forwarding to connect to different instances of Mirth.
