3 Replies Latest reply on Nov 11, 2016 1:46 PM by Panagiotis Chavariotis

    jboss-eap-6.2 - Remote deploy war JBAS012174 Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed

    Vince Sam Newbie

      Did the following steps:

      Added the new user and password using add_user.sh

      Groups = admin, deploy

      I went through the documentation and am unable to determine what is missing.

       

      Stack trace below:

      2016-11-09T15:10:44.8907710Z Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed

      2016-11-09T15:10:44.8907820Z at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:332)

      2016-11-09T15:10:44.8907950Z at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:225)

      2016-11-09T15:10:44.8908060Z at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)

      2016-11-09T15:10:44.8908160Z at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189

      2016-11-09T15:10:44.8908300Z at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)

      2016-11-09T15:10:44.8908400Z at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)

      2016-11-09T15:10:44.8908510Z at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)

      2016-11-09T15:10:44.8908650Z at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:180)

      2016-11-09T15:10:44.8908750Z at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)

      2016-11-09T15:10:44.8908850Z at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)

      2016-11-09T15:10:44.8909050Z at org.xnio.nio.NioHandle.run(NioHandle.java:90)

      2016-11-09T15:10:44.8909150Z at org.xnio.nio.WorkerThread.run(WorkerThread.java:187)

      2016-11-09T15:10:44.8909240Z at ...asynchronous invocation...(Unknown Source)

      2016-11-09T15:10:44.8909430Z at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270)

      2016-11-09T15:10:44.8909540Z at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)

      2016-11-09T15:10:44.8909630Z at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)

      2016-11-09T15:10:44.8909740Z at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:337)

      2016-11-09T15:10:44.8909870Z at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:79)

      2016-11-09T15:10:44.8909970Z at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:98)

        • 1. Re: jboss-eap-6.2 - Remote deploy war JBAS012174 Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
          Amit Nijhawan Newbie

          t looks like you have configured the security-realm that the remoting system is using to defer to JAAS.

           

          please enable TRACE level logging for the "org.jboss.security" category, recreate the issue and upload the server.log and boot.log:

           

          <logger category="org.jboss.security">

            <level name="TRACE"/>

          </logger>

          • 2. Re: jboss-eap-6.2 - Remote deploy war JBAS012174 Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
            Vince Sam Newbie

            Thanks Amit = this is resolved now - I had to add the user to Application Realm.

             

            Now the deploy was attempted but I get a different error now:

             

            Below is the stack trace.  Also we realized that the build of the war file is using Java 1.8 but Jboss environment is 1.7.  Not sure if this is the cause.  We will be fixing the build to point to Java 1.7

             

            10:07:11,798 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010403: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 4.0)

            10:07:11,955 ERROR [stderr] (MSC service thread 1-1) 2016-11-11 16:07:11.954 GMT Thread[MSC service thread 1-1,5,main] java.io.FileNotFoundException: derby.log (Permission denied)

            10:07:11,966 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010403: Deploying JDBC-compliant driver class org.apache.derby.jdbc.AutoloadedDriver (version 10.5)

            10:07:11,980 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."TestWeb.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."TestWeb.war".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "TestWeb.war"

                    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

                    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]

                    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]

                    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_111]

                    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_111]

                    at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_111]

            Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018027: Failed to add JBoss Web deployment service

                    at org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:353)

                    at org.jboss.as.web.deployment.WarDeploymentProcessor.deploy(WarDeploymentProcessor.java:126)

                    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

                    ... 5 more

            Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.web.deployment.default-host./TestWeb.realm is already registered

                    at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]

                    at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:227) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]

                    at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:561) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]

                    at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]

                    at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]

                    at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]

                    at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]

                    at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]

                    at org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:291)

                    ... 7 more

             

             

            10:07:12,004 ERROR [org.jboss.as.server] (management-handler-thread - 5) JBAS015870: Deploy of deployment "TestWeb.war" was rolled back with the following failure message:

            {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"TestWeb.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"TestWeb.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"TestWeb.war\"

                Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018027: Failed to add JBoss Web deployment service

                Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.web.deployment.default-host./TestWeb.realm is already registered"}}

            10:07:12,179 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment TestWeb.war (runtime-name: TestWeb.war) in 174ms

            • 3. Re: jboss-eap-6.2 - Remote deploy war JBAS012174 Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
              Panagiotis Chavariotis Novice

              First of all, please bear in mind that Derby DB is not supported.

              Secondly, it seems that your application is using a local Derby database, but apparently you do not have the permission to write on that directory.

              You should change the directory to some location where you have the write permission.