I have a custom login module that resides in login-config.xml, let's call it test1. If I deploy an ejb or webapp with the proper <security-domain> tag set to test1, everything works fine.
What I'd like to do is not have to provide a security-domain tag and default to some specific <application-policy>, similar the use of the application policy "other" when an unknown domain is used in <security-domain>. Is there any way to do this, or must the <security-domain> tag be present to use a custom login module? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3830008#3830008 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3830008 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
