[jboss-jira] [JBoss JIRA] Closed: (SECURITY-503) Fix NPE when TRACE level logging is enabled for org.jboss.security.auth.login.XMLLoginConfigImpl
Stefan Guilhen (JIRA)
jira-events at lists.jboss.org
Wed May 5 19:54:05 EDT 2010
[ https://jira.jboss.org/jira/browse/SECURITY-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Guilhen closed SECURITY-503.
-----------------------------------
Resolution: Done
NPE has been fixed on JBoss Security Branch_2_0 and on PicketBox branch.
> Fix NPE when TRACE level logging is enabled for org.jboss.security.auth.login.XMLLoginConfigImpl
> ------------------------------------------------------------------------------------------------
>
> Key: SECURITY-503
> URL: https://jira.jboss.org/jira/browse/SECURITY-503
> Project: PicketBox (JBoss Security and Identity Management)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JBossSX
> Affects Versions: JBossSecurity_2.0.4.SP3, PicketBox_v3_0_beta4
> Reporter: Marcus Moyses
> Assignee: Marcus Moyses
> Fix For: JBossSecurity_2.0.4.SP4, PicketBox_v3_0_beta5
>
>
> When TRACE level logging is enabled for org.jboss.security.auth.login.XMLLoginConfigImpl (or generic org.jboss.security package) a NPE is thrown if a login module option is empty, e.g.
> <module-option name="anOption"/>
> This causes login to fail when TRACE level logging is enabled.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list