[
https://issues.jboss.org/browse/SECURITY-864?page=com.atlassian.jira.plug...
]
Martin Letenay commented on SECURITY-864:
-----------------------------------------
We register it with plain {{new InitialContext().bind(policyRegistrationJndiName,
policyRegistration);}} and never noticed any read-only JNDI tree problems.
I've just tested it on Wildfly 10.0.0 and it went fine, JNDI tree accessible.
Maybe some configuration setting ?
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)