[
https://issues.jboss.org/browse/ELY-1584?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on ELY-1584:
----------------------------------
[~honza889] it might be sufficient. Mainly we'd want to see if it is possible to
create a log of failures from the test suite (without missing anything, which is a
challenge as each module may have a different logging configuration). And we'd want
to ensure that the logged permission violations do not change unexpectedly from one test
run to the next. Part of the challenge is that things do not always run in order though,
so we might need a special comparison tool for this.
I was thinking that it might even be a good idea to have options for a specialized format
which can be easily machine-parsed which includes the permission, the PD, and the stack
trace.
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)