Explicit LoginModule dependencies?

[ulmangt]

Is it possible to mark a JBoss LoginModule as being dependent on a Datasource? (so that the Datasource loads before anyone is allowed to authenticate using the LoginModule)

It seems like this would be necessary to use the provided org.jboss.security.auth.spi.DatabaseServerLoginModule. If not, what happens if something attempts to authenticate before the Datasource is bound to a JNDI name?

I know that mbeans can have an explicit dependencies, including on particular datasources. Here's an example snippit:

<mbean code="org.jboss.messaging.core.jmx.JDBCPersistenceManagerService"
      name="jboss.messaging:service=PersistenceManager"
      xmbean-dd="xmdesc/JDBCPersistenceManager-xmbean.xml">

      <depends>jboss.jca:service=DataSourceBinding,name=DefaultDS</depend>
      
      <!-- other stuff -->
</mbean>

I was hoping that there would be something similar for LoginModules.

P.S. I apologize for the somewhat similar thread in the Datasources forum (http://community.jboss.org/message/525966#525966). The question seems to apply equally to both areas.

[ulmangt]

I should add that my current workaround is to have my datasource's initialize method simply wait in a loop, doing a JNDI lookup every few seconds, until JBoss gets around to binding the datasource to a JNDI name.

This doesn't seem like a very clean approach. Is it a hack, or is there no other way to accomplish what I'm after?

[wolfgangknauf]

Hi,

how did you declare your login module?

If you use the "JBoss beans" approach introduced in JBoss 5, a "depends" should be possible:

{url}http://server.dzone.com/articles/security-features-jboss-510{url}

The "old" way of using "login-config.xml" does not provide this ability.

Hope this helps

Wolfgang