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

JMS client dependencies doesn't contain a default wildfly-config.xml

    XMLWordPrintable

Details

      • Unzip attached reproducer
      • configure the application server as described in the README.md
      • run the client (reproducer) as described in the README.md

    Description

      Using the wildfly-jms-client-bom dependency for JMS clients doesn't introduce a default wildfly-config.xml with Elytron client configuration. As the result, clients are not able to authenticate (e.g. using JBOSS-LOCAL-USER SASL mechanism).

      The default configuration in wildfly-config.xml should allow similar behavior as with legacy security. So the following call should pass:

      ConnectionFactory connectionFactory = (ConnectionFactory) namingContext.lookup("jms/RemoteConnectionFactory");
      

      Currently the call throws exception:

      SEVERE: Naming problem occured
      javax.naming.CommunicationException: WFNAM00018: Failed to connect to remote host [Root exception is javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server are supported]
      	at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNaming(RemoteNamingProvider.java:110)
      	at org.wildfly.naming.client.remote.RemoteContext.lookupNative(RemoteContext.java:91)
      	at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:78)
      	at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:64)
      	at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:123)
      	at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:113)
      	at javax.naming.InitialContext.lookup(InitialContext.java:417)
      	at org.wildfly.security.elytron.demo.JmsClient.main(JmsClient.java:45)
      Caused by: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server are supported
      	at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:412)
      	at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:239)
      	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
      	at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
      	at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
      	at org.xnio.nio.WorkerThread.run(WorkerThread.java:567)
      	at ...asynchronous invocation...(Unknown Source)
      	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:466)
      	at org.jboss.remoting3.FutureConnection.connect(FutureConnection.java:113)
      	at org.jboss.remoting3.FutureConnection.init(FutureConnection.java:75)
      	at org.jboss.remoting3.FutureConnection.get(FutureConnection.java:151)
      	at org.jboss.remoting3.EndpointImpl.getConnection(EndpointImpl.java:422)
      	at org.jboss.remoting3.UncloseableEndpoint.getConnection(UncloseableEndpoint.java:57)
      	at org.jboss.remoting3.Endpoint.getConnection(Endpoint.java:105)
      	at org.wildfly.naming.client.remote.RemoteNamingProvider.lambda$new$0(RemoteNamingProvider.java:68)
      	at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentity(RemoteNamingProvider.java:126)
      	at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNaming(RemoteNamingProvider.java:108)
      	... 7 more
      

      Attachments

        Issue Links

          Activity

            People

              darran.lofthouse@redhat.com Darran Lofthouse
              josef.cacek@gmail.com Josef Cacek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: