hishamrashdan · March 27, 2024 08:35 · Jan 19, 2024 · Apr 17, 2023 · Aug 15, 2022 · Jul 11, 2022
diff --git a/Managing SSL Connections in MC.md b/Managing SSL Connections in MC.md
@@ -18,7 +18,7 @@ The quick rundown is:
 5. Commercial solutions
   - Mirth has a commercial SSL extension - https://www.nextgen.com/products-and-services/integration-engine
   - Zen Healthcare IT has a an SSL extension with up-front pricing at - https://consultzen.com/zen-ssl-extension/
-  - Innovar has published an AWS instance with SSL support at - https://aws.amazon.com/marketplace/pp/prodview-rrvfqfm5vxbtk?sr=0-2&ref_=beagle&applicationId=AWSMPContessa
+  - Innovar has published an AWS instance with SSL support at - https://aws.amazon.com/marketplace/pp/prodview-rrvfqfm5vxbtk
 6. Channel code - You can use tools like Apache HTTP Commons or OKHttp in MC and use that code to deal with SSL
 
 The main consideration between these options are:

diff --git a/Managing SSL Connections in MC.md b/Managing SSL Connections in MC.md
@@ -8,6 +8,7 @@ The quick rundown is:
   - The connector may flag these connections with a warning or red x. Test the channel first as the validator makes assumptions about SSL that may not apply in this case.
 2. The built-in MC HTTP *Listener* connector will not do SSL directly. A plugin or a proxy is necessary.
   - Tony Germano has a plugin implemented for SSL listeners for HTTPS at https://github.com/tonygermano/connect-plugins
+  - Another open source SSL implementation is at https://github.com/tobchen/tc-ssl-plugin
 4. SSL firewalls or stunnel can also proxy the SSL connections. MC connects to the unsecured side of the tunnel and the SSL layer is handled on the other side. Open source tools:
   - stunnel https://www.stunnel.org/
   - haproxy http://www.haproxy.org/

diff --git a/Managing SSL Connections in MC.md b/Managing SSL Connections in MC.md
@@ -12,6 +12,8 @@ The quick rundown is:
   - stunnel https://www.stunnel.org/
   - haproxy http://www.haproxy.org/
   - nginx https://docs.nginx.com/
+
+    An open-source tool that lets Mirth Connect manage `stunnel` has been published at https://github.com/pacmano1/mirthstunnel
 5. Commercial solutions
   - Mirth has a commercial SSL extension - https://www.nextgen.com/products-and-services/integration-engine
   - Zen Healthcare IT has a an SSL extension with up-front pricing at - https://consultzen.com/zen-ssl-extension/

diff --git a/Managing SSL Connections in MC.md b/Managing SSL Connections in MC.md
@@ -8,7 +8,10 @@ The quick rundown is:
   - The connector may flag these connections with a warning or red x. Test the channel first as the validator makes assumptions about SSL that may not apply in this case.
 2. The built-in MC HTTP *Listener* connector will not do SSL directly. A plugin or a proxy is necessary.
   - Tony Germano has a plugin implemented for SSL listeners for HTTPS at https://github.com/tonygermano/connect-plugins
-4. SSL firewalls or stunnel can also proxy the SSL connections. MC connects to the unsecured side of the tunnel and the SSL layer is handled on the other side. 
+4. SSL firewalls or stunnel can also proxy the SSL connections. MC connects to the unsecured side of the tunnel and the SSL layer is handled on the other side. Open source tools:
+  - stunnel https://www.stunnel.org/
+  - haproxy http://www.haproxy.org/
+  - nginx https://docs.nginx.com/
 5. Commercial solutions
   - Mirth has a commercial SSL extension - https://www.nextgen.com/products-and-services/integration-engine
   - Zen Healthcare IT has a an SSL extension with up-front pricing at - https://consultzen.com/zen-ssl-extension/

diff --git a/Managing SSL Connections in MC.md b/Managing SSL Connections in MC.md
@@ -9,9 +9,10 @@ The quick rundown is:
 2. The built-in MC HTTP *Listener* connector will not do SSL directly. A plugin or a proxy is necessary.
   - Tony Germano has a plugin implemented for SSL listeners for HTTPS at https://github.com/tonygermano/connect-plugins
 4. SSL firewalls or stunnel can also proxy the SSL connections. MC connects to the unsecured side of the tunnel and the SSL layer is handled on the other side. 
-5. Commercial extensions
+5. Commercial solutions
   - Mirth has a commercial SSL extension - https://www.nextgen.com/products-and-services/integration-engine
-  - Zen Healthcare IT has a competing SSL offering at - https://consultzen.com/zen-ssl-extension/
+  - Zen Healthcare IT has a an SSL extension with up-front pricing at - https://consultzen.com/zen-ssl-extension/
+  - Innovar has published an AWS instance with SSL support at - https://aws.amazon.com/marketplace/pp/prodview-rrvfqfm5vxbtk?sr=0-2&ref_=beagle&applicationId=AWSMPContessa
 6. Channel code - You can use tools like Apache HTTP Commons or OKHttp in MC and use that code to deal with SSL
 
 The main consideration between these options are:

diff --git a/Managing SSL Connections in MC.md b/Managing SSL Connections in MC.md
@@ -3,7 +3,7 @@ Mirth Connect is awesome! One common question on the forums and Slack is how to
 The quick rundown is:
 1. The built-in MC HTTP *Sender* connector will do HTTPS if:
   - The endpoint has a certificate which is signed by a CA already present in the JVM truststore and has the right DN or SAN for the hostname. This is logically equivalent to the "green check" if you open the URL in a browser. 
-  - The certificate has been added to the truststore for the JVM that MC is running under (read https://kailo.tech/health-it/mirth-connect-add-ssl/_)
+  - The certificate has been added to the truststore for the JVM that MC is running under 
   - Changes to DNS or host files allow a hostname to match the DN or SAN already present in the cert (not reccomended)
   - The connector may flag these connections with a warning or red x. Test the channel first as the validator makes assumptions about SSL that may not apply in this case.
 2. The built-in MC HTTP *Listener* connector will not do SSL directly. A plugin or a proxy is necessary.

diff --git a/Managing SSL Connections in MC.md b/Managing SSL Connections in MC.md
@@ -15,6 +15,6 @@ The quick rundown is:
 6. Channel code - You can use tools like Apache HTTP Commons or OKHttp in MC and use that code to deal with SSL
 
 The main consideration between these options are:
-- Who is expected to manage the connections? Interface engineers benefit from options plugins that keep this inside MC
+- Who is expected to manage the connections? Interface engineers benefit from options plugins that keep this inside MC. Network engineers and devops will tend to prefer proxies and tunnels that are closer to the infrastructure layer than the application layer.
 - When will certs expire and what are the corporate policies about cert management? Most certificates are good for 1 to 3 years, that means that updates are required as the certificates expire. What option is easies for your organization to a) detect this expiration and b) update certificates BEFORE they expire as routine maintenance?
 - What other software in your environment uses SSL and how is that managed? 
diff --git a/Managing SSL Connections in MC.md b/Managing SSL Connections in MC.md
@@ -15,6 +15,6 @@ The quick rundown is:
 6. Channel code - You can use tools like Apache HTTP Commons or OKHttp in MC and use that code to deal with SSL
 
 The main consideration between these options are:
-- Who is expected to manage the connections? Interface engineers benefit from options 3 and 4. Network and DevOps are well positioned for 1 and 2.
+- Who is expected to manage the connections? Interface engineers benefit from options plugins that keep this inside MC
 - When will certs expire and what are the corporate policies about cert management? Most certificates are good for 1 to 3 years, that means that updates are required as the certificates expire. What option is easies for your organization to a) detect this expiration and b) update certificates BEFORE they expire as routine maintenance?
 - What other software in your environment uses SSL and how is that managed? 
diff --git a/Managing SSL Connections in MC.md b/Managing SSL Connections in MC.md
@@ -7,11 +7,12 @@ The quick rundown is:
   - Changes to DNS or host files allow a hostname to match the DN or SAN already present in the cert (not reccomended)
   - The connector may flag these connections with a warning or red x. Test the channel first as the validator makes assumptions about SSL that may not apply in this case.
 2. The built-in MC HTTP *Listener* connector will not do SSL directly. A plugin or a proxy is necessary.
-3. SSL firewalls or stunnel can also proxy the SSL connections. MC connects to the unsecured side of the tunnel and the SSL layer is handled on the other side. 
-4. Commercial extensions
+  - Tony Germano has a plugin implemented for SSL listeners for HTTPS at https://github.com/tonygermano/connect-plugins
+4. SSL firewalls or stunnel can also proxy the SSL connections. MC connects to the unsecured side of the tunnel and the SSL layer is handled on the other side. 
+5. Commercial extensions
   - Mirth has a commercial SSL extension - https://www.nextgen.com/products-and-services/integration-engine
   - Zen Healthcare IT has a competing SSL offering at - https://consultzen.com/zen-ssl-extension/
-5. Channel code - You can use tools like Apache HTTP Commons or OKHttp in MC and use that code to deal with SSL
+6. Channel code - You can use tools like Apache HTTP Commons or OKHttp in MC and use that code to deal with SSL
 
 The main consideration between these options are:
 - Who is expected to manage the connections? Interface engineers benefit from options 3 and 4. Network and DevOps are well positioned for 1 and 2.

diff --git a/Managing SSL Connections in MC.md b/Managing SSL Connections in MC.md
@@ -7,11 +7,11 @@ The quick rundown is:
   - Changes to DNS or host files allow a hostname to match the DN or SAN already present in the cert (not reccomended)
   - The connector may flag these connections with a warning or red x. Test the channel first as the validator makes assumptions about SSL that may not apply in this case.
 2. The built-in MC HTTP *Listener* connector will not do SSL directly. A plugin or a proxy is necessary.
-2. SSL firewalls or stunnel can also proxy the SSL connections. MC connects to the unsecured side of the tunnel and the SSL layer is handled on the other side. 
-3. Commercial extensions
+3. SSL firewalls or stunnel can also proxy the SSL connections. MC connects to the unsecured side of the tunnel and the SSL layer is handled on the other side. 
+4. Commercial extensions
   - Mirth has a commercial SSL extension - https://www.nextgen.com/products-and-services/integration-engine
   - Zen Healthcare IT has a competing SSL offering at - https://consultzen.com/zen-ssl-extension/
-4. Channel code - You can use tools like Apache HTTP Commons or OKHttp in MC and use that code to deal with SSL
+5. Channel code - You can use tools like Apache HTTP Commons or OKHttp in MC and use that code to deal with SSL
 
 The main consideration between these options are:
 - Who is expected to manage the connections? Interface engineers benefit from options 3 and 4. Network and DevOps are well positioned for 1 and 2.

diff --git a/Managing SSL Connections in MC.md b/Managing SSL Connections in MC.md
@@ -11,7 +11,7 @@ The quick rundown is:
 3. Commercial extensions
   - Mirth has a commercial SSL extension - https://www.nextgen.com/products-and-services/integration-engine
   - Zen Healthcare IT has a competing SSL offering at - https://consultzen.com/zen-ssl-extension/
-4. Channel code - You can use tools like Apache HTTP Commons in MC and use that code to deal with SSL
+4. Channel code - You can use tools like Apache HTTP Commons or OKHttp in MC and use that code to deal with SSL
 
 The main consideration between these options are:
 - Who is expected to manage the connections? Interface engineers benefit from options 3 and 4. Network and DevOps are well positioned for 1 and 2.

diff --git a/Managing SSL Connections in MC.md b/Managing SSL Connections in MC.md
@@ -1,10 +1,12 @@
 Mirth Connect is awesome! One common question on the forums and Slack is how to manage SSL connctions. These questions mainly focus on HTTPS but also include TCP connections.
 
 The quick rundown is:
-1. The built-in MC HTTP connector will do HTTPS if:
+1. The built-in MC HTTP *Sender* connector will do HTTPS if:
   - The endpoint has a certificate which is signed by a CA already present in the JVM truststore and has the right DN or SAN for the hostname. This is logically equivalent to the "green check" if you open the URL in a browser. 
   - The certificate has been added to the truststore for the JVM that MC is running under (read https://kailo.tech/health-it/mirth-connect-add-ssl/_)
   - Changes to DNS or host files allow a hostname to match the DN or SAN already present in the cert (not reccomended)
+  - The connector may flag these connections with a warning or red x. Test the channel first as the validator makes assumptions about SSL that may not apply in this case.
+2. The built-in MC HTTP *Listener* connector will not do SSL directly. A plugin or a proxy is necessary.
 2. SSL firewalls or stunnel can also proxy the SSL connections. MC connects to the unsecured side of the tunnel and the SSL layer is handled on the other side. 
 3. Commercial extensions
   - Mirth has a commercial SSL extension - https://www.nextgen.com/products-and-services/integration-engine

diff --git a/Managing SSL Connections in MC.md b/Managing SSL Connections in MC.md
@@ -3,7 +3,7 @@ Mirth Connect is awesome! One common question on the forums and Slack is how to
 The quick rundown is:
 1. The built-in MC HTTP connector will do HTTPS if:
   - The endpoint has a certificate which is signed by a CA already present in the JVM truststore and has the right DN or SAN for the hostname. This is logically equivalent to the "green check" if you open the URL in a browser. 
-  - The certificate has been added to the truststore for the JVM that MC is running under
+  - The certificate has been added to the truststore for the JVM that MC is running under (read https://kailo.tech/health-it/mirth-connect-add-ssl/_)
   - Changes to DNS or host files allow a hostname to match the DN or SAN already present in the cert (not reccomended)
 2. SSL firewalls or stunnel can also proxy the SSL connections. MC connects to the unsecured side of the tunnel and the SSL layer is handled on the other side. 
 3. Commercial extensions

diff --git a/Managing SSL Connections in MC.md b/Managing SSL Connections in MC.md
@@ -1,9 +1,10 @@
 Mirth Connect is awesome! One common question on the forums and Slack is how to manage SSL connctions. These questions mainly focus on HTTPS but also include TCP connections.
 
 The quick rundown is:
-1. The built-in MC HTTP connector will do HTTPS if either:
+1. The built-in MC HTTP connector will do HTTPS if:
   - The endpoint has a certificate which is signed by a CA already present in the JVM truststore and has the right DN or SAN for the hostname. This is logically equivalent to the "green check" if you open the URL in a browser. 
   - The certificate has been added to the truststore for the JVM that MC is running under
+  - Changes to DNS or host files allow a hostname to match the DN or SAN already present in the cert (not reccomended)
 2. SSL firewalls or stunnel can also proxy the SSL connections. MC connects to the unsecured side of the tunnel and the SSL layer is handled on the other side. 
 3. Commercial extensions
   - Mirth has a commercial SSL extension - https://www.nextgen.com/products-and-services/integration-engine

diff --git a/Managing SSL Connections in MC.md b/Managing SSL Connections in MC.md
@@ -2,10 +2,15 @@ Mirth Connect is awesome! One common question on the forums and Slack is how to
 
 The quick rundown is:
 1. The built-in MC HTTP connector will do HTTPS if either:
-  - The endpoint has a certificate which is signed by a CA already present in the JVM truststore and has the right DN or SAN for the hostname 
+  - The endpoint has a certificate which is signed by a CA already present in the JVM truststore and has the right DN or SAN for the hostname. This is logically equivalent to the "green check" if you open the URL in a browser. 
   - The certificate has been added to the truststore for the JVM that MC is running under
 2. SSL firewalls or stunnel can also proxy the SSL connections. MC connects to the unsecured side of the tunnel and the SSL layer is handled on the other side. 
 3. Commercial extensions
   - Mirth has a commercial SSL extension - https://www.nextgen.com/products-and-services/integration-engine
   - Zen Healthcare IT has a competing SSL offering at - https://consultzen.com/zen-ssl-extension/
-4. Channel code - You can use tools like Apache HTTP Commons in MC and use that code to deal with SSL
+4. Channel code - You can use tools like Apache HTTP Commons in MC and use that code to deal with SSL
+
+The main consideration between these options are:
+- Who is expected to manage the connections? Interface engineers benefit from options 3 and 4. Network and DevOps are well positioned for 1 and 2.
+- When will certs expire and what are the corporate policies about cert management? Most certificates are good for 1 to 3 years, that means that updates are required as the certificates expire. What option is easies for your organization to a) detect this expiration and b) update certificates BEFORE they expire as routine maintenance?
+- What other software in your environment uses SSL and how is that managed? 
diff --git a/Managing SSL Connections in MC.md b/Managing SSL Connections in MC.md
@@ -0,0 +1,11 @@
+Mirth Connect is awesome! One common question on the forums and Slack is how to manage SSL connctions. These questions mainly focus on HTTPS but also include TCP connections.
+
+The quick rundown is:
+1. The built-in MC HTTP connector will do HTTPS if either:
+  - The endpoint has a certificate which is signed by a CA already present in the JVM truststore and has the right DN or SAN for the hostname 
+  - The certificate has been added to the truststore for the JVM that MC is running under
+2. SSL firewalls or stunnel can also proxy the SSL connections. MC connects to the unsecured side of the tunnel and the SSL layer is handled on the other side. 
+3. Commercial extensions
+  - Mirth has a commercial SSL extension - https://www.nextgen.com/products-and-services/integration-engine
+  - Zen Healthcare IT has a competing SSL offering at - https://consultzen.com/zen-ssl-extension/
+4. Channel code - You can use tools like Apache HTTP Commons in MC and use that code to deal with SSL
No results found