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

[GSS](7.0.z) Remote standalone ejb client does not work with DIGEST-MD5

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • 7.0.0.GA
    • Remoting, Security
    • None
      • Run a clustered ejb on EAP 7.0 which bound to 10.10.10.10 with standalone-full-ha.xml file .
      • Run a standalone remote ejb client on different machine 20.20.20.20 .

    Description

      The clustered ejb bean is running on JBoss EAP 7.0 which bound to 10.10.10.10 with standalone-full-ha.xml file . The standalone remote ejb client is running on machine 20.20.20.20 . While executing the client got the below error :

      ^C[iingawal@iingawal cust]$ java -cp /jboss-eap-7.0/bin/client/jboss-client.jar:. ClusterTest
      May 19, 2017 7:29:27 PM org.jboss.ejb.client.EJBClient <clinit>
      INFO: JBoss EJB Client version 2.1.4.Final-redhat-1
      May 19, 2017 7:29:27 PM org.xnio.Xnio <clinit>
      INFO: XNIO version 3.3.6.Final-redhat-1
      May 19, 2017 7:29:27 PM org.xnio.nio.NioXnio <clinit>
      INFO: XNIO NIO Implementation Version 3.3.6.Final-redhat-1
      May 19, 2017 7:29:27 PM org.jboss.remoting3.EndpointImpl <clinit>
      INFO: JBoss Remoting version 4.0.18.Final-redhat-1
      May 19, 2017 7:29:27 PM org.jboss.ejb.client.remoting.VersionReceiver handleMessage
      INFO: EJBCLIENT000017: Received server version 2 and marshalling strategies [river]
      May 19, 2017 7:29:27 PM org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver associate
      INFO: EJBCLIENT000013: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@77cd7a0, receiver=Remoting connection EJB receiver [connection=org.jboss.ejb.client.remoting.ConnectionPool$PooledConnection@204f30ec,channel=jboss.ejb,nodename=node1]} on channel Channel ID aefca6a4 (outbound) of Remoting connection 56ef9176 to /10.10.10.10:8080
      May 19, 2017 7:29:27 PM org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager getEJBReceiver
      INFO: Could not create a connection for cluster node ClusterNode{clusterName='ejb', nodeName='node1', clientMappings=[ClientMapping{sourceNetworkAddress=/0:0:0:0:0:0:0:0, sourceNetworkMaskBits=0, destinationAddress='10.10.10.10', destinationPort=8080}], resolvedDestination=[Destination address=10.10.10.10, destination port=8080]} in cluster ejb
      javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed:
         JBOSS-LOCAL-USER: javax.security.sasl.SaslException: Failed to read server challenge [Caused by java.io.FileNotFoundException: /jboss-eap-7.0/standalone/tmp/auth/local4869264399574364994.challenge (No such file or directory)]
         DIGEST-MD5: javax.security.sasl.SaslException: DIGEST-MD5: authentication ID and password must be specified
      	at org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:114)
      	at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:389)
      	at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:241)
      	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
      	at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:199)
      	at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:113)
      	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
      	at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1092)
      	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:88)
      	at org.xnio.nio.WorkerThread.run(WorkerThread.java:559)
      	at ...asynchronous invocation...(Unknown Source)
      	at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:294)
      	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:416)
      	at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:153)
      	at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:133)
      	at org.jboss.ejb.client.remoting.ConnectionPool.getConnection(ConnectionPool.java:78)
      	at org.jboss.ejb.client.remoting.RemotingConnectionManager.getConnection(RemotingConnectionManager.java:51)
      	at org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager.getEJBReceiver(RemotingConnectionClusterNodeManager.java:79)
      	at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:469)
      	at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:443)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      	at java.lang.Thread.run(Thread.java:745)
      
      

      Below is jboss-ejb-client.properties:

      endpoint.name=client-endpoint
      remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
      
      remote.clusters=ejb
      remote.cluster.ejb.username=appuser
      remote.cluster.ejb.username=appuser123!
      
      # The names "server1" and "server2" are arbitrary; they just need to match up with
      # the various properties below that have "server1" or "server2" in them:
      remote.connections=server1
      
      remote.connection.server1.host=10.10.10.10
      remote.connection.server1.port=8080
      remote.connection.server1.username=appuser
      remote.connection.server1.password=appuser123!
      remote.connection.server1.SASL_POLICY_NOANONYMOUS=false
      remote.connection.server1.SASL_POLICY_NOPLAINTEXT=false
      

      Attachments

        Issue Links

          Activity

            People

              spyrkob Bartosz Spyrko-Smietanko
              rhn-support-iingawal Indrajit Ingawale
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: