With J2EE container managed security, the user must trigger the authentication by trying to access a protected area, EJB, webpage, whatever.
There are always 'ways' of doing things like this by proxy from your custom security login, but many are considered dirty hacks and you already say you don't wish to write any more code. The range of options open to you depends on your application. One thing that occurs to me off the top of my head is the 'anonymous' login that can be done. If you protect everything, then as soon as the user starts using the app, a login will occur and then in your custom login module you can fetch what info you need, if you can identify the user without any login name. Have fun! ;) <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3825690#3825690";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3825690>Reply to the post</a> ------------------------------------------------------- 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
