DatabaseServerLoginModule in JBoss-3.0.5RC1_tomcat-4.1.18

[jcordes]

Hi !

I'm experiencing a problem using DatabaseServerLoginModule. I've added the following section to login-config.xml :

<application-policy name = "CatalogDomain">

<login-module code ="org.jboss.security.auth.spi.DatabaseServerLoginModule" flag = "required">
<module-option name ="unauthenticatedIdentity">Anyone</module-option>
<module-option name="dsJndiName">java:/CatalogDS</module-option>
<module-option name="test">test</module-option>
<module-option name="principalsQuery">SELECT password FROM user WHERE login=?</module-option>
<module-option name="rolesQuery">SELECT role_name, role_group FROM role, user, user_role WHERE user.login=? AND user.id = user_role.user_id AND user_role.role_id = role.id</module-option>
<module-option name="managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=MySQLDS</module-option>
</login-module>

</application-policy>

I'm using it in combination with form-based login in tomcat. The settings have been done in jboss-web.xml, but it's not working. What I can see through jmx-console is that CatalogDomain is not bound to jndi. Strangely, no errors have showed up in the server logs. What happened, because this used to work in jboss-3.0.4 with exactly the same configuration ?

Any help would be greatly appreciated !!!

TIA,

Jochen.

[jcordes]

Now things are getting strange ... . With the Jetty-bundle everything works as expected. Anybody has a clue (I can see CatalogDomain in JNDI) ?

Bye,

Jochen.

[jferguson]

Hi Jochen,

Seems like the swap to php and back lost some forum stuff!

I'm just wondering if I missed any of your replies on this thread as of yesterday.

I was wondering about the 'built in valve' you found in the Tomcat connection jar.

Cheers,
Jon

[jcordes]

Hi Jon !

Yes, I replied yesterday (back at work though ;-)). Now I finally found that "internal valve" stuff. It's located at jboss-all\catalina\src\main\org\jboss\web\catalina\security\JBossSecurityMgrRealm.java.
. In my servlet I'm only reading out the form-fields and finally do a redirect, no other magic here, so it should work with your JSP right away.

Again no luck using the tomcat-4.1.12 bundle, the security domain is still not bound to JNDI. Regarding tomcat-4.1.18 there have been some ClassLoader-changes, so setting the loader-compliance to Java2 broke everything ...

Bye,

Jochen.

[jferguson]

Thanks Jochen for the help.

I'll have a look at that code.

Hmmm... sometimes these things just take some shaking out.. Wonder if the bug reports list the problem.

Cheers,
Jon