[jboss-jira] [JBoss JIRA] (WFLY-4376) Incorrect callback handler used during authentication (SASL)

RH Bugzilla Integration (JIRA) issues at jboss.org
Tue Sep 13 17:12:00 EDT 2016


    [ https://issues.jboss.org/browse/WFLY-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292938#comment-13292938 ] 

RH Bugzilla Integration commented on WFLY-4376:
-----------------------------------------------

Brad Maxwell <bmaxwell at redhat.com> changed the Status of [bug 901248|https://bugzilla.redhat.com/show_bug.cgi?id=901248] from POST to MODIFIED

> Incorrect callback handler used  during authentication (SASL)
> -------------------------------------------------------------
>
>                 Key: WFLY-4376
>                 URL: https://issues.jboss.org/browse/WFLY-4376
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering, EJB
>            Reporter: Enrique González Martínez
>            Assignee: Enrique González Martínez
>             Fix For: 10.0.0.CR5
>
>
> Cluster topology messages are not using the proper callbackhandler when the connection is being established.
> {code}
> 06:59:44,609 ERROR [org.jboss.remoting.remote.connection] (Remoting "config-based-ejb-client-endpoint" read-1) JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> 06:59:44,611 INFO  [org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager] (ejb-client-cluster-node-connection-creation-2-thread-2) Could not create a connection for cluster node ClusterNode{clusterName='ejb', nodeName='perf18', clientMappings=[ClientMapping{sourceNetworkAddress=/0:0:0:0:0:0:0:0, sourceNetworkMaskBits=0, destinationAddress='10.16.90.54', destinationPort=4447}], resolvedDestination=[Destination address=10.16.90.54, destination port=4447]} in cluster ejb
> java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> 	at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:91)
> 	at org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager.getEJBReceiver(RemotingConnectionClusterNodeManager.java:89)
> 	at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:406)
> 	at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:380)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:662)
> Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> 	at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:382)
> 	at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:225)
> 	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> 	at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> 	at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> 	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> 	at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> 	at org.xnio.nio.WorkerThread.run(WorkerThread.java:187)
> 	at ...asynchronous invocation...(Unknown Source)
> 	at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270)
> 	at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:386)
> 	at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:151)
> 	at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:132)
> 	at org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager.getEJBReceiver(RemotingConnectionClusterNodeManager.java:87)
> 	... 7 more
> {code}
> Before that, this log is produced:
> {code}
> DEBUG: Client authentication failed for mechanism DIGEST-MD5: javax.security.sasl.SaslException: DIGEST-MD5: Cannot perform callback to acquire realm, authentication ID or password [Caused by javax.security.auth.callback.UnsupportedCallbackException]
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)



More information about the jboss-jira mailing list