9 Replies Latest reply on Mar 5, 2014 4:26 PM by ozizka

SaslException: Authentication failed: all available authentication mechanisms failed

ozizka Feb 10, 2012 11:44 PM

Hi, I'm getting "SaslException: Authentication failed: all available authentication mechanisms failed".

It's most likely a misconfiguration. But since the exception doesn't tell what auth mechanisms it tried, I don't know that either.

What should I look for?

04:29:26,216 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015876: Starting deployment of "client.jar"
04:29:26,454 ERROR [org.jboss.remoting.remote] (Remoting "jbossas-multinode-client" read-1) JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
04:29:26,456 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-13) MSC00001: Failed to start service jboss.ejb3.dd-based-ejb-client-context."client.jar": org.jboss.msc.service.StartException in service jboss.ejb3.dd-based-ejb-client-context."client.jar": Failed to start service
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
    at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
Caused by: 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.as.ejb3.remote.DescriptorBasedEJBClientContextService.createRemotingConnections(DescriptorBasedEJBClientContextService.java:124)
    at org.jboss.as.ejb3.remote.DescriptorBasedEJBClientContextService.start(DescriptorBasedEJBClientContextService.java:86)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
    ... 3 more
Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
    at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:315) [jboss-remoting-3.2.0.GA.jar:3.2.0.GA]
    at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:214) [jboss-remoting-3.2.0.GA.jar:3.2.0.GA]
    at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) [xnio-api-3.0.0.GA.jar:3.0.0.GA]
    at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) [xnio-api-3.0.0.GA.jar:3.0.0.GA]
    at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) [xnio-api-3.0.0.GA.jar:3.0.0.GA]
    at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) [xnio-api-3.0.0.GA.jar:3.0.0.GA]
    at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) [xnio-api-3.0.0.GA.jar:3.0.0.GA]
    at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:180) [xnio-api-3.0.0.GA.jar:3.0.0.GA]
    at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) [xnio-api-3.0.0.GA.jar:3.0.0.GA]
    at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) [xnio-api-3.0.0.GA.jar:3.0.0.GA]
    at org.xnio.nio.NioHandle.run(NioHandle.java:90)
    at org.xnio.nio.WorkerThread.run(WorkerThread.java:184)
    at ...asynchronous invocation...(Unknown Source)
    at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:268) [jboss-remoting-3.2.0.GA.jar:3.2.0.GA]
    at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:250) [jboss-remoting-3.2.0.GA.jar:3.2.0.GA]
    at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:359) [jboss-remoting-3.2.0.GA.jar:3.2.0.GA]
    at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:347) [jboss-remoting-3.2.0.GA.jar:3.2.0.GA]
    at org.jboss.as.remoting.RemoteOutboundConnectionService.connect(RemoteOutboundConnectionService.java:130) [jboss-as-remoting-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
    at org.jboss.as.ejb3.remote.DescriptorBasedEJBClientContextService.createRemotingConnections(DescriptorBasedEJBClientContextService.java:122)
    ... 6 more

1. Re: SaslException: Authentication failed: all available authentication mechanisms failed

ozizka Feb 11, 2012 1:52 AM (in response to ozizka)

It was missing users and roles definitions in standalone/configuration/application-*.properties, of course.
Actions
2. Re: SaslException: Authentication failed: all available authentication mechanisms failed

madchedar0 May 11, 2012 8:10 PM (in response to ozizka)

Thanks for replying with what the solution was - I ran into this same issue.
Actions
3. Re: SaslException: Authentication failed: all available authentication mechanisms failed

npatel2012 Jul 6, 2012 6:33 AM (in response to ozizka)

Hello,

I have ran into a similar issue. Could you please let me know which users are to be added to connect to host successfully? I am using a default configuration and am facing this issue.

Thanks
Actions
4. Re: SaslException: Authentication failed: all available authentication mechanisms failed

ozizka Jul 6, 2012 1:23 PM (in response to npatel2012)

Depends on the particular application... what you can't connect to? You will find the necessary role in it's source code or documentation.
Actions
5. Re: SaslException: Authentication failed: all available authentication mechanisms failed

npatel2012 Jul 7, 2012 5:43 PM (in response to ozizka)

I managed to resolve this issue by:

1. Adding "username="jboss" security-realm="ManagementRealm" to host.xml (my host controller) which was previously missing in my configuration which I believe forces the host controller to validate using the username "jboss"

          <remote host="${jboss.domain.master.address}" port="${jboss.domain.master.port:9999}" username="jboss" security-realm="ManagementRealm"/>

2. And then as mentioned in this post I added the user "jboss" to the domain controller.

3. Then I added Base64 encoded password which was generated when I created the user "jboss" to the host controller. This looks something like the following:

     <server-identities>
                    
         <secret value="aG9zdDFwYXNzd29yZA=="/>
     </server-identities>
Actions
6. Re: SaslException: Authentication failed: all available authentication mechanisms failed

softmahi Feb 27, 2013 10:21 AM (in response to npatel2012)

Thanks This works fine for me.
Actions
7. Re: SaslException: Authentication failed: all available authentication mechanisms failed

wang_wangui Apr 14, 2013 12:07 PM (in response to softmahi)

i use standalone mode for my deployment, and the error some like above, i don't know how to solve it. the error is:

22:41:56,323 ERROR [org.jboss.remoting.remote.connection] (Remoting "config-based-naming-client-endpoint" read-1) JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
22:41:56,338 INFO [org.springframework.beans.factory.support.DefaultListableBeanFactory] (MSC service thread 1-3) Destroying singletons in factory {org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [config,properties,sales]; root of BeanFactory hierarchy}
22:41:56,338 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/jbosstest]] (MSC service thread 1-3) Exception sending context initialized event to listener instance of class com.sitech.frame.core.config.WebContextLoaderListener: java.lang.ExceptionInInitializerError
at com.sitech.frame.core.config.Config.getConfig(Config.java:68) [classes:]
Actions
8. Re: SaslException: Authentication failed: all available authentication mechanisms failed

oortdg Jan 10, 2014 4:06 PM (in response to npatel2012)

Why isn't this mentioned by no one. I've seen many how to setup an managed domain, but no one talks about an user name. I've spend two day's to at last find this.

So i hope this will be put in the documentation also for eap 6.2 and wildfly
Actions
9. Re: SaslException: Authentication failed: all available authentication mechanisms failed

ozizka Mar 5, 2014 4:26 PM (in response to oortdg)

Now it's mentioned in EAP 6.2 Admin guide. And perhaps will also appear in Getting started and in WildFly too. Also the exception msg might provide a hint.
Actions

Go to original post