The example doesn't use custom login modules. It's just using the UserNamePassword login module in the jboss login-config.xml file. My production system is using a custom login module, but the results are the same in both setups, so I'm reasonably certain that the behaviour isn't due to my custom module.
The application is accessing the jaas configuation in the normal way via the jboss-web.xml file: <security-domain>java:/jaas/other</security-domain> This calls the default application-policy in the login-config.xml which is configured to use the UsersRolesLoginModule by default. The whole application is the expanded struts-blank.war folder in the deploy directory. The login modules themselves are presumably stored somewhere in the jboss class library heirarchy. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3928338#3928338 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3928338 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
