From: Scott M S. (JIRA) <jir...@jb...> - 2005-07-30 15:06:09
|
[ http://jira.jboss.com/jira/browse/JBAS-1971?page=all ] Scott M Stark closed JBAS-1971: ------------------------------- Resolution: Done This information is provided at trace level since debug level is enabled by default in the server log. <!-- Log security related events at trace level --> <category name="org.jboss.security"> <priority value="TRACE" class="org.jboss.logging.XLevel"/> </category> > Provide debug information if creation of a login module faiils > -------------------------------------------------------------- > > Key: JBAS-1971 > URL: http://jira.jboss.com/jira/browse/JBAS-1971 > Project: JBoss Application Server > Type: Feature Request > Components: Security > Environment: not env dependent > Reporter: Ramon Grunder > Priority: Optional > > > If the initialization of a login module fails for some reason, no information is logged. > Stupid example that happened to me: calling log.debug before super.initialize(...) in the initialize(...) method of a custom login module. The log call provoked a NullPointerException that is catched silently somewhere and the login module will not be available to the application, resulting in Authentication exceptions upon the first EJB method call. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |