2 Replies Latest reply on Nov 10, 2003 5:16 AM by wolfc

    UsersRolesLoginModule not running in correct ContextThread

    wolfc

      In 3.2.2 it appears that the UsersRolesLoginModule is not running in the right context thead. This worked fine in 3.2.1.

      First I logon to my bios.war:
      2003-11-06 17:24:09,562 TRACE [org.jboss.security.auth.spi.UsersRolesLoginModule] initialize
      2003-11-06 17:24:09,562 TRACE [org.jboss.security.auth.spi.UsersRolesLoginModule] Properties file=file:/C:/Java/jboss-3.2.2/server/beep/tmp/deploy/tmp112beep.ear-contents/bios.war/WEB-INF/classes/users.properties
      2003-11-06 17:24:09,562 TRACE [org.jboss.security.auth.spi.UsersRolesLoginModule] Properties file=file:/C:/Java/jboss-3.2.2/server/beep/tmp/deploy/tmp112beep.ear-contents/bios.war/WEB-INF/classes/roles.properties
      2003-11-06 17:24:09,562 TRACE [org.jboss.security.auth.spi.UsersRolesLoginModule] login
      2003-11-06 17:24:09,562 TRACE [org.jboss.security.auth.spi.UsersRolesLoginModule] User 'royal' authenticated, loginOk=true
      2003-11-06 17:24:09,562 TRACE [org.jboss.security.auth.spi.UsersRolesLoginModule] commit, loginOk=true

      Then I try to logon to my beep.war:
      2003-11-06 17:33:10,562 TRACE [org.jboss.security.auth.spi.UsersRolesLoginModule] initialize
      2003-11-06 17:33:10,562 TRACE [org.jboss.security.auth.spi.UsersRolesLoginModule] Properties file=file:/C:/Java/jboss-3.2.2/server/beep/tmp/deploy/tmp112beep.ear-contents/bios.war/WEB-INF/classes/users.properties
      2003-11-06 17:33:10,562 TRACE [org.jboss.security.auth.spi.UsersRolesLoginModule] Properties file=file:/C:/Java/jboss-3.2.2/server/beep/tmp/deploy/tmp112beep.ear-contents/bios.war/WEB-INF/classes/roles.properties
      2003-11-06 17:33:10,562 TRACE [org.jboss.security.auth.spi.UsersRolesLoginModule] login
      2003-11-06 17:33:10,562 DEBUG [org.jboss.security.auth.spi.UsersRolesLoginModule] Bad password for username=helpdesk
      2003-11-06 17:33:10,562 TRACE [org.jboss.security.auth.spi.UsersRolesLoginModule] abort

      As you can see the wrong properties files are loaded.

      Did I miss something in some spec about class loading behaviour or is this a bug in jBoss 3.2.2?