Login-config.xml

[kapil munjal]

Hi,

I need some guidance related to login-config.xml configuration.

I have 2 application EAR which needs to be deployed on the same instance. But these applications are using different "jbossmq" configuration. One application is using Database and other is using file state service.

Please tell me how I can change one application to use File state service instead of Database.

Application 1 -

It uses Database settings in the "jbossmq" application policy. This application has one MDB 2.1.

      <application-policy name = "jbossmq">
       <authentication>
          <login-module code = "org.jboss.security.auth.spi.DatabaseServerLoginModule"
             flag = "required">
             <module-option name = "unauthenticatedIdentity">guest</module-option>
             <module-option name = "dsJndiName">java:/HSQLDS</module-option>
             <module-option name = "principalsQuery">SELECT PASSWD FROM JMS_USERS WHERE USERID=?</module-option>
             <module-option name = "rolesQuery">SELECT ROLEID, 'Roles' FROM JMS_ROLES WHERE USERID=?</module-option>
          </login-module>
       </authentication>
    </application-policy>   

Application 2 -

It uses file-state service in the "jbossmq" application policy. This application has Entity beans 2.1.

   <application-policy name = "jbossmq">
       <authentication>
          <login-module code = "org.jboss.mq.sm.file.DynamicLoginModule"
             flag = "required">
             <module-option name = "unauthenticatedIdentity">guest</module-option>
             <module-option name = "sm.objectname">jboss.mq:service=StateManager</module-option>
          </login-module>
       </authentication>
    </application-policy> 

I have tried changing the Application 1 to use file-state-service. But not able to make it work. I used the steps described in the jboss documentation.

Thanks

[Peter Johnson]

First, you cannot use the same name for two different application policies.

Why are you using the "jbossmq" policy? That should be used for messaging only (or at least, it is the example policy to use for messaging). I recommend setting up two new policies.

If after making these changesi t still does not work, post the exception stack you are getting, or provide details about the error(s) you are seeing.

[kapil munjal]

Well, I didn't setup these 2 policies. These 2 applications were running on different JBoss instances. And their internal functionality uses "jbossmq" for EJBs.

Application 1, which has an MDB used for Message Queuing.

If I keep the "jbossmq" policy with Application 1, then application 2 doesn't work and it throws "EJB spec violation" error.

If I keep the "jbossmq" policy with Application 2, then application 1 doesn't work and it throws "XAConnectionFactory not bound" error.

Now, the situation is that I need make these applications work on single JBoss instance.

Thanks

[Peter Johnson]

You will have to change one of the names and reconfigure the app to use the new name.

[Hakan Erdogan]

Here is the fastest solution:
Merge two login modules into one application-policy and mark their flag as sufficient.

   <application-policy name = "jbossmq">  
        <authentication>  
           <login-module code = "org.jboss.mq.sm.file.DynamicLoginModule"  
              flag = "sufficient">  
              <module-option name = "unauthenticatedIdentity">guest</module-option>  
              <module-option name = "sm.objectname">jboss.mq:service=StateManager</module-option>  
           </login-module>  
           <login-module code = "org.jboss.security.auth.spi.DatabaseServerLoginModule"  
              flag = "sufficient">  
              <module-option name = "unauthenticatedIdentity">guest</module-option>  
              <module-option name = "dsJndiName">java:/HSQLDS</module-option>  
              <module-option name = "principalsQuery">SELECT PASSWD FROM JMS_USERS WHERE USERID=?</module-option>  
              <module-option name = "rolesQuery">SELECT ROLEID, 'Roles' FROM JMS_ROLES WHERE USERID=?</module-option>  
           </login-module>  
        </authentication>  
     </application-policy>   

[Ri Ay]

As stated above, if in the same situation we have two different login modules but with for two different datasources (both being DatabaseServerLoginModule) described in the <connection-url> of *-ds.xml file in deploy directory of jboss as -

<connection-url> datasource1,datasource2...</connection-url>

Then in such a situation how to configure *-ds.xml or login-config.xml ?

Thanks.

Hakan Erdogan wrote:Here is the fastest solution:
Merge two login modules into one application-policy and mark their flag as sufficient.

   <application-policy name = "jbossmq">  
        <authentication>  
           <login-module code = "org.jboss.mq.sm.file.DynamicLoginModule"  
              flag = "sufficient">  
              <module-option name = "unauthenticatedIdentity">guest</module-option>  
              <module-option name = "sm.objectname">jboss.mq:service=StateManager</module-option>  
           </login-module>  
           <login-module code = "org.jboss.security.auth.spi.DatabaseServerLoginModule"  
              flag = "sufficient">  
              <module-option name = "unauthenticatedIdentity">guest</module-option>  
              <module-option name = "dsJndiName">java:/HSQLDS</module-option>  
              <module-option name = "principalsQuery">SELECT PASSWD FROM JMS_USERS WHERE USERID=?</module-option>  
              <module-option name = "rolesQuery">SELECT ROLEID, 'Roles' FROM JMS_ROLES WHERE USERID=?</module-option>  
           </login-module>  
        </authentication>  
     </application-policy>