[
https://issues.jboss.org/browse/ELY-1584?page=com.atlassian.jira.plugin.s...
]
Jan Kalina commented on ELY-1584:
---------------------------------
[~dmlloyd] what exactly mean "outside of the standard log infrastructure" ?
We already have DEBUG messages in *org.wildfly.security.access*:
{code}
17:15:03,705 DEBUG (main) [org.wildfly.security.access]
<WildFlySecurityManager.java:226> Permission check failed (permission
"("java.io.FilePermission"
"/home/jkalina/work/wildfly-elytron/target/test-classes/org/junit/runner/notification/RunNotifier$7.class"
"read")" in code source
"(file:/home/jkalina/work/wildfly-elytron/target/classes/ <no signer
certificates>)" of "sun.misc.Launcher$AppClassLoader@18b4aac2")
{code}
jboss logger allows to redirect it into standalone log file - is not it sufficient?
Add ability to log security manager violations to out-of-band log
file
----------------------------------------------------------------------
Key: ELY-1584
URL:
https://issues.jboss.org/browse/ELY-1584
Project: WildFly Elytron
Issue Type: Enhancement
Components: Security Manager
Reporter: David Lloyd
It would be useful for CI if we could set a system property which would log security
manager permission check violations (and the details thereof) to a log file, outside of
the standard log infrastructure. This would potentially allow us to fail CI when
unexpected "hidden" permission violations occur by way of a post-build script
analyzes the log output.
This might also be useful for troubleshooting more obscure security manager related
problems.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)