Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-25043

http and native interfaces requires sasl-authentication-factory assigned

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 8.0.0.GA
    • Management, Security
    • None
    • False
    • None
    • False
    • Hide
      • build JBoss EAP/WildFly from latest commit (I had d7f4cfc15d5e841606ed2699a54704029dd9ae78)
      • extract and start the domain: ./bin/domain.sh
      • connect to CLI: ./bin/jboss-cli.sh -c
      • create native-inteface:
        /host=primary/core-service=management/management-interface=native-interface:add(interface=management,port=9999)
        reload --host=primary
        
      • servers won't boot and you can see following in the ./server/domain/servers/server-one/log/server.log:
        2023-06-21 10:28:17,740 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 2) MSC000001: Failed to start service jboss.server-boot-operations: org.jboss.msc.service.StartException in service jboss.server-boot-operations: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://127.0.0.1:9999. The connection failed
                at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT//org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:73)
                at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
                at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
                at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
                at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
                at java.base/java.lang.Thread.run(Thread.java:829)
                at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)
        Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://127.0.0.1:9999. The connection failed
                at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT//org.jboss.as.protocol.ProtocolConnectionUtils.checkFuture(ProtocolConnectionUtils.java:142)
                at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT//org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:122)
                at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT//org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
                at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT//org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
                at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT//org.jboss.as.server.mgmt.domain.HostControllerConnection$1.run(HostControllerConnection.java:147)
                at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT//org.jboss.as.server.mgmt.domain.HostControllerConnection$1.run(HostControllerConnection.java:143)
                at org.wildfly.common@1.6.0.Final//org.wildfly.common.context.Contextual.runExceptionAction(Contextual.java:108)
                at org.wildfly.security.elytron-base@2.2.1.Final//org.wildfly.security.auth.client.AuthenticationContext.run(AuthenticationContext.java:280)
                at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT//org.jboss.as.server.mgmt.domain.HostControllerConnection.internalConnect(HostControllerConnection.java:143)
                at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT//org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:126)
                at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT//org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:113)
                at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT//org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:69)
                ... 6 more
        Caused by: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server (ANONYMOUS) are supported
                at org.jboss.remoting@5.0.27.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:443)
                at org.jboss.remoting@5.0.27.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:244)
                at org.jboss.xnio@3.8.9.Final//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
                at org.jboss.xnio@3.8.9.Final//org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
                at org.jboss.xnio.nio@3.8.9.Final//org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
                at org.jboss.xnio.nio@3.8.9.Final//org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
                at ...asynchronous invocation...(Unknown Source)
                at org.jboss.remoting@5.0.27.Final//org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:600)
                at org.jboss.remoting@5.0.27.Final//org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:561)
                at org.jboss.remoting@5.0.27.Final//org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:549)
                at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT//org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:224)
                at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT//org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118)
                ... 16 more
        
        2023-06-21 10:28:17,741 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: java.util.concurrent.ExecutionException: JBTHR00005: Operation failed
                at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT//org.jboss.as.server.ServerStartTask$2$1.load(ServerStartTask.java:183)
                at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT//org.jboss.as.server.ServerService.boot(ServerService.java:399)
                at org.jboss.as.controller@21.0.0.Beta5-SNAPSHOT//org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:370)
                at java.base/java.lang.Thread.run(Thread.java:829)
        Caused by: java.util.concurrent.ExecutionException: JBTHR00005: Operation failed
                at org.jboss.threads@2.4.0.Final//org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:253)
                at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT//org.jboss.as.server.mgmt.domain.ServerBootOperationsService$2.get(ServerBootOperationsService.java:114)
                at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT//org.jboss.as.server.mgmt.domain.ServerBootOperationsService$2.get(ServerBootOperationsService.java:96)
                at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT//org.jboss.as.server.ServerStartTask$2$1.load(ServerStartTask.java:180)
                ... 3 more
        Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://127.0.0.1:9999. The connection failed
                at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT//org.jboss.as.protocol.ProtocolConnectionUtils.checkFuture(ProtocolConnectionUtils.java:142)
                at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT//org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:122)
                at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT//org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
                at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT//org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
                at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT//org.jboss.as.server.mgmt.domain.HostControllerConnection$1.run(HostControllerConnection.java:147)
                at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT//org.jboss.as.server.mgmt.domain.HostControllerConnection$1.run(HostControllerConnection.java:143)
                at org.wildfly.common@1.6.0.Final//org.wildfly.common.context.Contextual.runExceptionAction(Contextual.java:108)
                at org.wildfly.security.elytron-base@2.2.1.Final//org.wildfly.security.auth.client.AuthenticationContext.run(AuthenticationContext.java:280)
                at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT//org.jboss.as.server.mgmt.domain.HostControllerConnection.internalConnect(HostControllerConnection.java:143)
                at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT//org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:126)
                at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT//org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:113)
                at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT//org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:69)
                at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
                at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
                at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
                at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
                at java.base/java.lang.Thread.run(Thread.java:829)
                at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)
        Caused by: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server (ANONYMOUS) are supported
                at org.jboss.remoting@5.0.27.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:443)
                at org.jboss.remoting@5.0.27.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:244)
                at org.jboss.xnio@3.8.9.Final//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
                at org.jboss.xnio@3.8.9.Final//org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
                at org.jboss.xnio.nio@3.8.9.Final//org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
                at org.jboss.xnio.nio@3.8.9.Final//org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
                at ...asynchronous invocation...(Unknown Source)
                at org.jboss.remoting@5.0.27.Final//org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:600)
                at org.jboss.remoting@5.0.27.Final//org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:561)
                at org.jboss.remoting@5.0.27.Final//org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:549)
                at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT//org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:224)
                at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT//org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118)
                ... 16 more
        
      • you can fix the server by specifying the sasl-authentication-factory explicitely:
        /host=primary/core-service=management/management-interface=native-interface:write-attribute(name=sasl-authentication-factory,value=management-sasl-authentication)
        

      Similar issue goes also with http-interface but in this case the sasl-authentication-factory is set from start in default server configuration. But since that element isn't necessary, we can simply break the server via CLI like this:

      /host=primary/core-service=management/management-interface=native-interface:remove()
      /host=primary/core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade,value={enabled=true})
      reload --host=primary
      

      Server won't boot after this change with the very same error described above.

      Note: there is http-authentication-factory defined in the http-inteface but it's not enough. Also note that if we would keep the native-interface defined in previous step, the server will boot just fine.

      Show
      build JBoss EAP/WildFly from latest commit (I had d7f4cfc15d5e841606ed2699a54704029dd9ae78 ) extract and start the domain: ./bin/domain.sh connect to CLI: ./bin/jboss-cli.sh -c create native-inteface : /host=primary/core-service=management/management- interface = native - interface :add( interface =management,port=9999) reload --host=primary servers won't boot and you can see following in the ./server/domain/servers/server-one/log/server.log : 2023-06-21 10:28:17,740 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 2) MSC000001: Failed to start service jboss.server-boot-operations: org.jboss.msc.service.StartException in service jboss.server-boot-operations: java.net.ConnectException: WFLYPRT0053: Could not connect to remote: //127.0.0.1:9999. The connection failed at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT //org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:73) at org.jboss.threads@2.4.0.Final //org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.4.0.Final //org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) at org.jboss.threads@2.4.0.Final //org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads@2.4.0.Final //org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348) at java.base/java.lang. Thread .run( Thread .java:829) at org.jboss.threads@2.4.0.Final //org.jboss.threads.JBossThread.run(JBossThread.java:513) Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote: //127.0.0.1:9999. The connection failed at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT //org.jboss.as.protocol.ProtocolConnectionUtils.checkFuture(ProtocolConnectionUtils.java:142) at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT //org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:122) at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT //org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259) at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT //org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT //org.jboss.as.server.mgmt.domain.HostControllerConnection$1.run(HostControllerConnection.java:147) at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT //org.jboss.as.server.mgmt.domain.HostControllerConnection$1.run(HostControllerConnection.java:143) at org.wildfly.common@1.6.0.Final //org.wildfly.common.context.Contextual.runExceptionAction(Contextual.java:108) at org.wildfly.security.elytron-base@2.2.1.Final //org.wildfly.security.auth.client.AuthenticationContext.run(AuthenticationContext.java:280) at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT //org.jboss.as.server.mgmt.domain.HostControllerConnection.internalConnect(HostControllerConnection.java:143) at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT //org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:126) at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT //org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:113) at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT //org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:69) ... 6 more Caused by: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server (ANONYMOUS) are supported at org.jboss.remoting@5.0.27.Final //org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:443) at org.jboss.remoting@5.0.27.Final //org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:244) at org.jboss.xnio@3.8.9.Final //org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.jboss.xnio@3.8.9.Final //org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) at org.jboss.xnio.nio@3.8.9.Final //org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) at org.jboss.xnio.nio@3.8.9.Final //org.xnio.nio.WorkerThread.run(WorkerThread.java:591) at ...asynchronous invocation...(Unknown Source) at org.jboss.remoting@5.0.27.Final //org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:600) at org.jboss.remoting@5.0.27.Final //org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:561) at org.jboss.remoting@5.0.27.Final //org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:549) at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT //org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:224) at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT //org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118) ... 16 more 2023-06-21 10:28:17,741 ERROR [org.jboss.as.server] (Controller Boot Thread ) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: java.util.concurrent.ExecutionException: JBTHR00005: Operation failed at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT //org.jboss.as.server.ServerStartTask$2$1.load(ServerStartTask.java:183) at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT //org.jboss.as.server.ServerService.boot(ServerService.java:399) at org.jboss.as.controller@21.0.0.Beta5-SNAPSHOT //org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:370) at java.base/java.lang. Thread .run( Thread .java:829) Caused by: java.util.concurrent.ExecutionException: JBTHR00005: Operation failed at org.jboss.threads@2.4.0.Final //org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:253) at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT //org.jboss.as.server.mgmt.domain.ServerBootOperationsService$2.get(ServerBootOperationsService.java:114) at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT //org.jboss.as.server.mgmt.domain.ServerBootOperationsService$2.get(ServerBootOperationsService.java:96) at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT //org.jboss.as.server.ServerStartTask$2$1.load(ServerStartTask.java:180) ... 3 more Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote: //127.0.0.1:9999. The connection failed at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT //org.jboss.as.protocol.ProtocolConnectionUtils.checkFuture(ProtocolConnectionUtils.java:142) at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT //org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:122) at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT //org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259) at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT //org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT //org.jboss.as.server.mgmt.domain.HostControllerConnection$1.run(HostControllerConnection.java:147) at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT //org.jboss.as.server.mgmt.domain.HostControllerConnection$1.run(HostControllerConnection.java:143) at org.wildfly.common@1.6.0.Final //org.wildfly.common.context.Contextual.runExceptionAction(Contextual.java:108) at org.wildfly.security.elytron-base@2.2.1.Final //org.wildfly.security.auth.client.AuthenticationContext.run(AuthenticationContext.java:280) at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT //org.jboss.as.server.mgmt.domain.HostControllerConnection.internalConnect(HostControllerConnection.java:143) at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT //org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:126) at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT //org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:113) at org.jboss.as.server@21.0.0.Beta5-SNAPSHOT //org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:69) at org.jboss.threads@2.4.0.Final //org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.4.0.Final //org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) at org.jboss.threads@2.4.0.Final //org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads@2.4.0.Final //org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348) at java.base/java.lang. Thread .run( Thread .java:829) at org.jboss.threads@2.4.0.Final //org.jboss.threads.JBossThread.run(JBossThread.java:513) Caused by: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server (ANONYMOUS) are supported at org.jboss.remoting@5.0.27.Final //org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:443) at org.jboss.remoting@5.0.27.Final //org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:244) at org.jboss.xnio@3.8.9.Final //org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.jboss.xnio@3.8.9.Final //org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) at org.jboss.xnio.nio@3.8.9.Final //org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) at org.jboss.xnio.nio@3.8.9.Final //org.xnio.nio.WorkerThread.run(WorkerThread.java:591) at ...asynchronous invocation...(Unknown Source) at org.jboss.remoting@5.0.27.Final //org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:600) at org.jboss.remoting@5.0.27.Final //org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:561) at org.jboss.remoting@5.0.27.Final //org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:549) at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT //org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:224) at org.jboss.as.protocol@21.0.0.Beta5-SNAPSHOT //org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118) ... 16 more you can fix the server by specifying the sasl-authentication-factory explicitely: /host=primary/core-service=management/management- interface = native - interface :write-attribute(name=sasl-authentication-factory,value=management-sasl-authentication) Similar issue goes also with http-interface but in this case the sasl-authentication-factory is set from start in default server configuration. But since that element isn't necessary, we can simply break the server via CLI like this: /host=primary/core-service=management/management- interface = native - interface :remove() /host=primary/core-service=management/management- interface =http- interface :write-attribute(name=http-upgrade,value={enabled= true }) reload --host=primary Server won't boot after this change with the very same error described above. Note: there is http-authentication-factory defined in the http-inteface but it's not enough. Also note that if we would keep the native-interface defined in previous step, the server will boot just fine.

      After this commit which is part of this PR (JBEAP-24543), both http-interface and native-interface seem to require sasl-authentication-factory assigned otherwise server won't boot (I tried this with domain mode). More info in reproduction steps.

      This issue isn't present in standalone mode.

      Is this expected change of requirement after the move from the legacy security to the elytron? If not, we should fix this requirement so that server don't fail during the boot. If it is expected, then I think we should probably update both XSD definitions and elements info showed in CLI with regards the sasl-authentication-factory (which will lead to the update of the required attributes defined):

      • /host=primary/core-service=management/management-interface=native-interface:read-resource-description
      • /host=primary/core-service=management/management-interface=http-interface:read-resource-description

            Unassigned Unassigned
            jstourac@redhat.com Jan Stourac
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: