deployment - javax.security.auth.login.LoginException: unable to find LoginModule class: org.jboss.security.ClientLoginModule -

its been more 3 days couldn't figure out wrong jenkins.

i have jenkins job, pull source bitbucket , build , deploy in jboss 5.1.

but @ time of deployment getting bellow exception tried multiple solution getting same annoying error.

stack-trace

[info] build success  [info] ------------------------------------------------------------------------  [info] total time: 2.534 s  [info] finished at: 2015-07-08t03:19:04+05:30  [info] final memory: 13m/176m  [info] ------------------------------------------------------------------------  [jenkins] archiving /var/lib/jenkins/jobs/springhelloworld/workspace/pom.xml com.programcreek/helloworld/0.0.1-snapshot/helloworld-0.0.1-snapshot.pom  [jenkins] archiving /var/lib/jenkins/jobs/springhelloworld/workspace/target/helloworld.war com.programcreek/helloworld/0.0.1-snapshot/helloworld-0.0.1-snapshot.war  channel stopped  deploying /var/lib/jenkins/jobs/springhelloworld/workspace/target/helloworld.war container jboss 5.x remote    undeployment phase of redeploy action has failed: org.codehaus.cargo.util.cargoexception: cannot undeploy deployable org.codehaus.cargo.container.deployable.war[helloworld.war]  error: build step failed exception  org.codehaus.cargo.util.cargoexception: cannot deploy deployable org.codehaus.cargo.container.deployable.war[helloworld.war]  	at org.codehaus.cargo.container.jboss.jboss5xremotedeployer.deploy(jboss5xremotedeployer.java:216)  	at org.codehaus.cargo.container.spi.deployer.abstractdeployer.redeploy(abstractdeployer.java:212)  	at hudson.plugins.deploy.cargocontaineradapter.deploy(cargocontaineradapter.java:73)  	at hudson.plugins.deploy.cargocontaineradapter$1.invoke(cargocontaineradapter.java:116)  	at hudson.plugins.deploy.cargocontaineradapter$1.invoke(cargocontaineradapter.java:103)  	at hudson.filepath.act(filepath.java:989)  	at hudson.filepath.act(filepath.java:967)  	at hudson.plugins.deploy.cargocontaineradapter.redeploy(cargocontaineradapter.java:103)  	at hudson.plugins.deploy.deploypublisher.perform(deploypublisher.java:61)  	at hudson.tasks.buildstepmonitor$3.perform(buildstepmonitor.java:45)  	at hudson.model.abstractbuild$abstractbuildexecution.perform(abstractbuild.java:761)  	at hudson.model.abstractbuild$abstractbuildexecution.performallbuildsteps(abstractbuild.java:721)  	at hudson.maven.mavenmodulesetbuild$mavenmodulesetbuildexecution.post2(mavenmodulesetbuild.java:1053)  	at hudson.model.abstractbuild$abstractbuildexecution.post(abstractbuild.java:670)  	at hudson.model.run.execute(run.java:1766)  	at hudson.maven.mavenmodulesetbuild.run(mavenmodulesetbuild.java:537)  	at hudson.model.resourcecontroller.execute(resourcecontroller.java:98)  	at hudson.model.executor.run(executor.java:374)  caused by: javax.security.auth.login.loginexception: unable find loginmodule class: org.jboss.security.clientloginmodule  	at javax.security.auth.login.logincontext.invoke(logincontext.java:800)  	at javax.security.auth.login.logincontext.access$000(logincontext.java:203)  	at javax.security.auth.login.logincontext$4.run(logincontext.java:690)  	at javax.security.auth.login.logincontext$4.run(logincontext.java:688)  	at java.security.accesscontroller.doprivileged(native method)  	at javax.security.auth.login.logincontext.invokepriv(logincontext.java:687)  	at javax.security.auth.login.logincontext.login(logincontext.java:595)  	at org.codehaus.cargo.tools.jboss.jbossdeployer.getdeploymentmanager(jbossdeployer.java:176)  	at org.codehaus.cargo.tools.jboss.jbossdeployer.deploy(jbossdeployer.java:71)  	at org.codehaus.cargo.container.jboss.jboss5xremotedeployer.deploy(jboss5xremotedeployer.java:212)  	... 17 more  javax.security.auth.login.loginexception: unable find loginmodule class: org.jboss.security.clientloginmodule  	at javax.security.auth.login.logincontext.invoke(logincontext.java:800)  	at javax.security.auth.login.logincontext.access$000(logincontext.java:203)  	at javax.security.auth.login.logincontext$4.run(logincontext.java:690)  	at javax.security.auth.login.logincontext$4.run(logincontext.java:688)  	at java.security.accesscontroller.doprivileged(native method)  	at javax.security.auth.login.logincontext.invokepriv(logincontext.java:687)  	at javax.security.auth.login.logincontext.login(logincontext.java:595)  	at org.codehaus.cargo.tools.jboss.jbossdeployer.getdeploymentmanager(jbossdeployer.java:176)  	at org.codehaus.cargo.tools.jboss.jbossdeployer.deploy(jbossdeployer.java:71)  	at org.codehaus.cargo.container.jboss.jboss5xremotedeployer.deploy(jboss5xremotedeployer.java:212)  	at org.codehaus.cargo.container.spi.deployer.abstractdeployer.redeploy(abstractdeployer.java:212)  	at hudson.plugins.deploy.cargocontaineradapter.deploy(cargocontaineradapter.java:73)  	at hudson.plugins.deploy.cargocontaineradapter$1.invoke(cargocontaineradapter.java:116)  	at hudson.plugins.deploy.cargocontaineradapter$1.invoke(cargocontaineradapter.java:103)  	at hudson.filepath.act(filepath.java:989)  	at hudson.filepath.act(filepath.java:967)  	at hudson.plugins.deploy.cargocontaineradapter.redeploy(cargocontaineradapter.java:103)  	at hudson.plugins.deploy.deploypublisher.perform(deploypublisher.java:61)  	at hudson.tasks.buildstepmonitor$3.perform(buildstepmonitor.java:45)  	at hudson.model.abstractbuild$abstractbuildexecution.perform(abstractbuild.java:761)  	at hudson.model.abstractbuild$abstractbuildexecution.performallbuildsteps(abstractbuild.java:721)  	at hudson.maven.mavenmodulesetbuild$mavenmodulesetbuildexecution.post2(mavenmodulesetbuild.java:1053)  	at hudson.model.abstractbuild$abstractbuildexecution.post(abstractbuild.java:670)  	at hudson.model.run.execute(run.java:1766)  	at hudson.maven.mavenmodulesetbuild.run(mavenmodulesetbuild.java:537)  	at hudson.model.resourcecontroller.execute(resourcecontroller.java:98)  	at hudson.model.executor.run(executor.java:374)  build step 'deploy war/ear container' marked build failure  finished: failure      

i tried multiple ways.

1. after searching lot found jbossx/jbossx-security-client.jar.zip missing in jboss lib, downloaded jar , pasted lib. but problem still there tried modify login-config.xml not working me.

the content of login-config.xml this.

<?xml version='1.0'?>    <!-- xml based jaas login configuration read  org.jboss.security.auth.login.xmlloginconfig mbean. add  application-policy element each security domain.    outline of application-policy is:  <application-policy name="security-domain-name">    <authentication>      <login-module code="login.module1.class.name" flag="control_flag">        <module-option name = "option1-name">option1-value</module-option>        <module-option name = "option2-name">option2-value</module-option>        ...      </login-module>        <login-module code="login.module2.class.name" flag="control_flag">        ...      </login-module>      ...    </authentication>  </application-policy>    $id: login-config.xml 87078 2009-04-09 14:23:47z bstansberry@jboss.com $  $revision: 87078 $  -->    <policy>    <!-- used clients within application server vm such    mbeans , servlets access ejbs.    -->    <application-policy name="client-login">      <authentication>        <login-module code="org.jboss.security.clientloginmodule"          flag="required">           <!-- existing security context restored on logout -->           <module-option name="restore-login-identity">true</module-option>        </login-module>      </authentication>    </application-policy>      <!-- security domains testing new jca framework -->    <application-policy name="hsqldbrealm">      <authentication>        <login-module code="org.jboss.resource.security.configuredidentityloginmodule"          flag="required">          <module-option name="principal">sa</module-option>          <module-option name="username">sa</module-option>          <module-option name="password"></module-option>          <module-option name="managedconnectionfactoryname">jboss.jca:service=localtxcm,name=defaultds</module-option>        </login-module>      </authentication>    </application-policy>      <application-policy name="jmsxarealm">      <authentication>        <login-module code="org.jboss.resource.security.configuredidentityloginmodule"          flag="required">          <module-option name="principal">guest</module-option>          <module-option name="username">guest</module-option>          <module-option name="password">guest</module-option>          <module-option name="managedconnectionfactoryname">jboss.jca:service=txcm,name=jmsxa</module-option>        </login-module>      </authentication>    </application-policy>      <!-- template configuration jmx-console web application.      defaults usersrolesloginmodule same other , should      changed stronger authentication mechanism required.    -->    <application-policy name="jmx-console">      <authentication>        <login-module code="org.jboss.security.auth.spi.usersrolesloginmodule"          flag="required">          <module-option name="usersproperties">props/jmx-console-users.properties</module-option>          <module-option name="rolesproperties">props/jmx-console-roles.properties</module-option>        </login-module>      </authentication>    </application-policy>      <!-- template configuration web-console web application.      defaults usersrolesloginmodule same other , should      changed stronger authentication mechanism required.    -->    <application-policy name="web-console">      <authentication>        <login-module code="org.jboss.security.auth.spi.usersrolesloginmodule"          flag="required">          <module-option name="usersproperties">web-console-users.properties</module-option>          <module-option name="rolesproperties">web-console-roles.properties</module-option>        </login-module>      </authentication>    </application-policy>      <!--      template configuration jbossws security domain.      defaults usersrolesloginmodule same other , should      changed stronger authentication mechanism required.    -->    <application-policy name="jbossws">      <authentication>        <login-module code="org.jboss.security.auth.spi.usersrolesloginmodule"          flag="required">          <module-option name="usersproperties">props/jbossws-users.properties</module-option>          <module-option name="rolesproperties">props/jbossws-roles.properties</module-option>          <module-option name="unauthenticatedidentity">anonymous</module-option>        </login-module>      </authentication>    </application-policy>      <!-- default login configuration used security domain    not have application-policy entry matching name    -->    <application-policy name="other">      <!-- simple server login module, can used when number      of users relatively small. uses 2 properties files:      users.properties, holds users (key) , password (value).      roles.properties, holds users (key) , comma-separated list of      roles (value).      unauthenticatedidentity property defines name of principal      used when null username , password presented      case unuathenticated web client or mdb. if want      allow such users authenticated add property, e.g.,      unauthenticatedidentity="nobody"      -->      <authentication>        <login-module code="org.jboss.security.auth.spi.usersrolesloginmodule"          flag="required"/>      </authentication>    </application-policy>    </policy>

i not sure do file. have clue regarding ??

after searching lot, found deploy plug-in self has problem. used method so. since, able build project, left deploy project in jboss. instead of using deploy plug-in using shell script. "scp" copy .war file in jboss deploy folder , restart jboss shell script well.

and done