Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-5076

remoting http-connector silently accepts invalid security-realm

XMLWordPrintable

      If the remoting subsystem is changed to the following:

             <subsystem xmlns="urn:jboss:domain:remoting:4.0">
            <http-connector name="http-remoting-connector" connector-ref="default" security-realm="OtherRealm"/>
        </subsystem>

      The server starts without error, however attempting to establish a connection fails.

      ./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

      Although the CLI can not do anything over port 8080 it should be able to initiate a remoting connection i.e.

      ./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

              darran.lofthouse@redhat.com Darran Lofthouse
              darran.lofthouse@redhat.com Darran Lofthouse
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: