[
https://issues.jboss.org/browse/SECURITY-864?page=com.atlassian.jira.plug...
]
Philippe Marschall commented on SECURITY-864:
---------------------------------------------
[~mletenay] No, read only JNDI seems to be feature of the modular service container based
runtimes (JBoss AS 7+). JNDI is only writable during deployment. Maybe your module gets
called during deployment of the application so you don't notice. Or a
{{WritableServiceBasedNamingStore#pushOwner}} is missing in our case.
We use EJB remoting and our login module gets called after deployment when the first EJB
call is made. Right now we look at implementing a custom JNDI object factory, we'll
keep you posted.
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)