]
Ranabir Chakraborty commented on WFLY-13828:
--------------------------------------------
Hello [~mgrossmann] Sorry, I was busy with some other issues. Currently, I'm working
on it. This is the first feature request of mine, there are many steps to follow before
doing the coding part, will take some time.
remote+tls is not supported by EJBClient and
remote-outbound-connection
-----------------------------------------------------------------------
Key: WFLY-13828
URL:
https://issues.redhat.com/browse/WFLY-13828
Project: WildFly
Issue Type: Feature Request
Components: Remoting
Affects Versions: 20.0.1.Final
Reporter: Matthias Großmann
Assignee: Ranabir Chakraborty
Priority: Major
Hi,
in our company we would like to use the newest Wildfly together with legacy servers like
JBoss AS 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}