[
https://issues.jboss.org/browse/SECURITY-864?page=com.atlassian.jira.plug...
]
Philippe Marschall commented on SECURITY-864:
---------------------------------------------
[~mletenay] we went with a custom [JNDI
ObjectFactory|https://github.com/marschall/policy-registration-factory], that keeps our
LoginModule clean from work arounds and solves the issue we had with read only JNDI.
NameNotFoundException due to policyRegistration -- service
jboss.naming.context.java.policyRegistration
-------------------------------------------------------------------------------------------------------
Key: SECURITY-864
URL:
https://issues.jboss.org/browse/SECURITY-864
Project: PicketBox
Issue Type: Bug
Components: PicketBox
Reporter: Chao Wang
Assignee: Stefan Guilhen
"NameNotFoundException due to policyRegistration -- service
jboss.naming.context.java.policyRegistration" is recorded in server.log during
quickstart example run by changing log level:
{noformat}
<logger category="org.jboss.as.security">
<level name="TRACE"/>
</logger>
<logger category="org.jboss.security">
<level name="TRACE"/>
</logger>
{noformat}
See detailed description in community discussion
[#907134|https://developer.jboss.org/message/907134]
I choose Jira component picketbox since the exception is titled as "PBOX000293:
Exception caught: javax.naming.NameNotFoundException"
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)