1 Reply Latest reply on Apr 26, 2004 2:29 PM by jbs650

    Authentication in Scheduler vs Stand Alone Client

    jbs650 Newbie

      I have developed some utility programs that are able to run as stand alone Java clients against my application and use LoginInitialContextFactory to provide their principal and credential information.

      However, When I try to start these utility programs from a Scheduler task (basically just launches the utilities in a new Thread), authentication is not performed correctly and I get:

      java.rmi.ServerException: EJBException:; nested exception is:
       javax.ejb.EJBException: checkSecurityAssociation; CausedByException is:
       Authentication exception, principal=null


      Does anyone have any ideas on why authentication works correctly for standalone clients but doesn't for my Scheduler launched ones?

      Here are my jndi.properties:
      java.naming.factory.initial=org.jboss.security.jndi.LoginInitialContextFactory
      java.naming.provider.url=jnp://localhost:1099
      java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
      java.naming.security.protocol=JIS
      java.naming.security.principal=systemservice
      java.naming.security.credentials=XXXXXX


      Here is my client-auth.conf:
      JIS {
       // jBoss LoginModule
       org.jboss.security.ClientLoginModule required
       ;
      };


      Here is the application policy from login-config.xml:
      <application-policy name = "JIS">
       <authentication>
       <login-module code = "org.jboss.security.auth.spi.UsersRolesLoginModule"
       flag = "required" />
       <login-module code = "org.jboss.security.ClientLoginModule"
       flag = "required" />
       </authentication>
      </application-policy>


      Thanks
      --jason