[ https://issues.redhat.com/browse/WFLY-13828?page=com.atlassian.jira.plugi... ] Matthias Großmann updated WFLY-13828: ------------------------------------- Description: Hi, in our company we would like to use the newest Wildfly together with legacy servers like Jboss 7 over SSL. This is possible with the Uri scheme "remote+tls" provided by jboss-remoting https://github.com/jboss-remoting/jboss-remoting/blob/master/src/main/jav... {code:java} final RemoteConnectionProviderFactory remoteConnectionProviderFactory = new RemoteConnectionProviderFactory(); ... endpoint.addConnectionProvider("remote+tls", remoteConnectionProviderFactory, OptionMap.create(Options.SECURE, Boolean.TRUE)); {code} But that uri scheme is not supported by the jboss-ejb-client in current version https://github.com/wildfly/jboss-ejb-client/blob/master/src/main/java/org... {code} public boolean supportsProtocol(final String uriScheme) { switch (uriScheme) { case "remote": case "remote+http": case "remote+https": // compatibility case "remoting": case "http-remoting": case "https-remoting": { return true; } default: { return false; } } } {code} and also the remote-outbound-connection does not allow that protocol: https://github.com/wildfly/wildfly-core/blob/master/remoting/subsystem/sr... {code} public enum Protocol { REMOTE("remote"), REMOTE_HTTP("remote+http"), HTTP_REMOTING("http-remoting"), HTTPS_REMOTING("https-remoting"), REMOTE_HTTPS("remote+https"); {code} was: Hi, in our company we would like to use the newest Wildfly together with legacy servers like Jboss 7 over SSL. This is possible with the Uri scheme "remote+tls" provided by jboss-remoting https://github.com/jboss-remoting/jboss-remoting/blob/master/src/main/jav... {code:java} // remote (SSL is explicit in URL) final RemoteConnectionProviderFactory remoteConnectionProviderFactory = new RemoteConnectionProviderFactory(); ... endpoint.addConnectionProvider("remote+tls", remoteConnectionProviderFactory, OptionMap.create(Options.SECURE, Boolean.TRUE)); {code} But that uri scheme is not supported by the jboss-ejb-client in current version https://github.com/wildfly/jboss-ejb-client/blob/master/src/main/java/org... {code} public boolean supportsProtocol(final String uriScheme) { switch (uriScheme) { case "remote": case "remote+http": case "remote+https": // compatibility case "remoting": case "http-remoting": case "https-remoting": { return true; } default: { return false; } } } {code} and also the remote-outbound-connection does not allow that protocol: https://github.com/wildfly/wildfly-core/blob/master/remoting/subsystem/sr... {code} public enum Protocol { REMOTE("remote"), REMOTE_HTTP("remote+http"), HTTP_REMOTING("http-remoting"), HTTPS_REMOTING("https-remoting"), REMOTE_HTTPS("remote+https"); {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)