0 Replies Latest reply on Jul 12, 2004 9:22 AM by Mike Osganian

    Upgrading from 3.2.3 to 3.2.5 and getting Security errors

    Mike Osganian Newbie

      In trying to upgrade from 3.2.3 to 3.2.5 and my EAR file now gets the following errors:

      2004-07-12 09:03:19,799 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] initialize
      2004-07-12 09:03:19,799 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] Saw unauthenticatedIdentity=guest
      2004-07-12 09:03:19,799 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] DatabaseServerLoginModule, dsJndiName=MyData
      2004-07-12 09:03:19,799 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] principalsQuery=SELECT PASSWD FROM JMS_USERS WHERE USERID=?
      2004-07-12 09:03:19,799 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] rolesQuery=SELECT ROLEID FROM JMS_ROLES WHERE USERID=?
      2004-07-12 09:03:19,799 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] login
      2004-07-12 09:03:19,799 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] Authenticating as unauthenticatedIdentity=guest
      2004-07-12 09:03:19,799 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] User 'guest' authenticated, loginOk=true
      2004-07-12 09:03:19,799 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] commit, loginOk=true
      2004-07-12 09:03:19,809 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] abort
      2004-07-12 09:03:19,809 DEBUG [org.jboss.security.plugins.JaasSecurityManager.jbossmq] Login failure
      javax.security.auth.login.LoginException: javax.naming.NameNotFoundException: MyData not bound
      at org.jboss.security.auth.spi.DatabaseServerLoginModule.getRoleSets(DatabaseServerLoginModule.java:217)
      at org.jboss.security.auth.spi.AbstractServerLoginModule.commit(AbstractServerLoginModule.java:187)


      Don't understand why MyData (to MySQL) is not bound. JBoss has no problem creating my JMS_* tables using it earlier in the log.

      And immediately after:

      2004-07-12 09:03:19,809 TRACE [org.jboss.mq.security.SecurityManager] User: null is NOT authenticated
      2004-07-12 09:03:19,809 TRACE [org.jboss.mq.server.TracingInterceptor] EXCEPTION : authenticate:
      javax.jms.JMSSecurityException: User: null is NOT authenticated
      at org.jboss.mq.security.SecurityManager.authenticate(SecurityManager.java:215)
      at org.jboss.mq.security.ServerSecurityInterceptor.authenticate(ServerSecurityInterceptor.java:51)
      at org.jboss.mq.server.TracingInterceptor.authenticate(TracingInterceptor.java:787)
      at org.jboss.mq.server.JMSServerInvoker.authenticate(JMSServerInvoker.java:287)
      at org.jboss.mq.il.jvm.JVMServerIL.authenticate(JVMServerIL.java:301)
      at org.jboss.mq.Connection.authenticate(Connection.java:1153)


      I'm looking everywhere and can't figure out whats going on. I have 2 MDBs that have subscribers specified that are in my new JMS_USERs and JMS_ROLES tables.

      Does anybody have any idea what I am missing?

      Thanks for any help
      Mike