[jboss-jira] [JBoss JIRA] (WFLY-13724) remoting http-connector silently accepts invalid security-realm
Darran Lofthouse (Jira)
issues at jboss.org
Fri Jul 31 11:13:01 EDT 2020
Darran Lofthouse created WFLY-13724:
---------------------------------------
Summary: remoting http-connector silently accepts invalid security-realm
Key: WFLY-13724
URL: https://issues.redhat.com/browse/WFLY-13724
Project: WildFly
Issue Type: Bug
Components: Remoting
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 21.0.0.Beta1
If the remoting subsystem is changed to the following:
{code:xml}
<subsystem xmlns="urn:jboss:domain:remoting:4.0">
<http-connector name="http-remoting-connector" connector-ref="default" security-realm="OtherRealm"/>
</subsystem>
{code}
The server starts without error, however attempting to establish a connection fails.
{code}
./jboss-cli.sh -c --controller=remote+http://localhost:8080
Failed to connect to the controller: The controller is not available at localhost:8080: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:8080. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:8080. The connection failed: Invalid response code 200
{code}
Although the CLI can not do anything over port 8080 it should be able to initiate a remoting connection i.e.
{code}
./jboss-cli.sh -c --controller=remote+http://localhost:8080
Failed to connect to the controller: The controller is not available at localhost:8080: org.jboss.remoting3.ServiceOpenException: Unknown service name management: Unknown service name management
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
More information about the jboss-jira
mailing list