We're updating the issue view to help you get more done. 

remote deployment to JBoss AS 7.1.0.Final in standalone configuration leads to javax.security.sasl.SaslException

Description

When i try to deploy to a remote jboss server i see following error:

1 2 3 4 5 6 7 8 9 10 [INFO] --- cargo-maven2-plugin:1.2.0:deployer-deploy (deploy-project) @ zet-deploy --- [INFO] [2.DeployerDeployMojo] Resolved container artifact org.codehaus.cargo:cargo-core-container-jboss:jar:1.2.0 for container jboss71x Feb 22, 2012 1:49:43 PM org.xnio.Xnio <clinit> INFO: XNIO Version 3.0.3.GA Feb 22, 2012 1:49:43 PM org.xnio.nio.NioXnio <clinit> INFO: XNIO NIO Implementation Version 3.0.3.GA Feb 22, 2012 1:49:43 PM org.jboss.remoting3.EndpointImpl <clinit> INFO: JBoss Remoting version 3.2.2.GA Feb 22, 2012 1:49:44 PM org.jboss.remoting3.remote.RemoteConnection handleException ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed

Everything works fine without authentification with a local deployment.
The jboss configuration seems to be working, because i can connect by command line using jboss-admin.sh and passing my username and password.

plugin configuration

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 <plugin> <groupId>org.codehaus.cargo</groupId> <artifactId>cargo-maven2-plugin</artifactId> <version>1.2.0</version> <dependencies> <dependency> <groupId>org.jboss.as</groupId> <artifactId>jboss-as-controller-client</artifactId> <version>7.1.0.Final</version> </dependency> </dependencies> <configuration> <container> <containerId>jboss71x</containerId> <type>remote</type> </container> <configuration> <type>runtime</type> <properties> <cargo.hostname>${deploy.webapp.host}</cargo.hostname> <cargo.jboss.management.port>${deploy.webapp.management.port}</cargo.jboss.management.port> <cargo.remote.username>${deploy.webapp.username}</cargo.remote.username> <cargo.remote.password>${deploy.webapp.password}</cargo.remote.password> </properties> </configuration> <deployer> <type>remote</type> <deployables> <deployable> <artifactId>zet-web</artifactId> <type>war</type> <properties> <context>zet</context> </properties> <pingURL>http://${deploy.webapp.host}:${deploy.webapp.port}/${deploy.webapp.context}/</pingURL> <pingTimeout>120000</pingTimeout> </deployable> </deployables> </deployer> </configuration> <executions> <execution> <id>deploy-project</id> <phase>install</phase> <goals> <goal>deployer-deploy</goal> </goals> </execution> </executions> </plugin>

The used jboss configuration is appended.
Seems to be a plug-in bug.

Status

Assignee

Savas Ali Tokmen

Reporter

Stephan Lau

Components

Fix versions

Affects versions

1.2.0

Priority

Major