[ https://issues.jboss.org/browse/TEIIDSB-86?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIIDSB-86 at 5/14/19 5:37 PM: ---------------------------------------------------------------- After making a full assessment, the recommendation is to: If end-to-end (internal and external) is needed, offer an option for 1-way secure transports using the service generated certificate. External exposure with a loadbalancer, which works for both transports with or without ssl. If secure external only is needed, we need to be able to start both the secure and non-secure transports. At a later time, if secure external only is needed, we could offer an option for 1-way secure transports using a stunnel with external access provided via routes - but of course that requires that clients use a stunnel client as well. The advantages here are being able to use external routes and the same transport for secure and non-secure. was (Author: shawkins): After making a full assessment, the recommendation is to: If end-to-end (internal and external) is needed, offer an option for 1-way secure transports using the service generated certificate. External exposure with a loadbalancer, which works for both transports with or without ssl. At an even later time, if secure external only is needed, we could offer an option for 1-way secure transports using a stunnel with external access provided via routes - but of course that requires that clients use a stunnel client as well. -- This message was sent by Atlassian Jira (v7.12.1#712002)