[WFLY-456] Audit Logging - squashed the below commits since master has changed so much [WFLY-456] Minor OperationContext impl cleanups [WFLY-456] Bring in John Bailey's audit log classes [WFLY-456] Add real audit loggers into the model controllers; integrate management handlers [WFLY-456] Log the full set of information [WFLY-456] Fix problems from rebase [WFLY-456] Use SecurityContext when invoking JMX methods via remoting [WFLY-456] Move core security classes into own module [WFLY-456] Rework things and make the controller logger work [WFLY-456] Include the access mechanism in the log, move some more classes to core-security [WFLY-456] Make audit logger available to JMX [WFLY-456] Pluggable MBeanServer delegate to audit logger, and loads of exception handling [WFLY-456] Jmx audit log proxy [WFLY-456] Separate the configuration for the core controller and jmx audit logs [WFLY-456] Set the booting flag in the jmx layer [WFLY-456] Integrate audit logging resource and ops into JMX extension so it can be configured there [WFLY-456] Correct copyright notices in my new files [WFLY-456] fix problems from rebase [WFLY-456] Get rid of the original hashing implementation [WFLY-456] Add missing originalResultTxControl from rebase [WFLY-456] Add config for appenders [WFLY-456] Basic file appender and json formatter. The output needs cleaning up and everything is currently hardcoded [WFLY-456] Back up the previous log file. Basic syslog appender (awaiting the improved logmanager SyslogHandler) [WFLY-456] Use the org.wildfly:wildfly-xxx names. Start configuring file appenders [WFLY-456] Configure model for syslog appender [WFLY-456] Log audit log records for ParallelBootOperationContext and ReadOnlyContext [WFLY-456] Make whether to log on boot configurable [WFLY-456] Be able to add/remove appender references at runtime and update the appenders at runtime [WFLY-456] Add boot-log to jmx audit-log as well and update xsd's for both core and jmx [WFLY-456] Make additive changes to appenders take effect right away, and delay changes/removals until the current audit record has been written [WFLY-456] Add schema support and parsing for managed server path overrides, and clean up the handlers [WFLY-456] Use 'handler' rather than 'appender' [WFLY-456] Pass in audit log operations to managed servers on boot [WFLY-456] Separate handler chains for host and managed server audit logs [WFLY-456] i18n and get rid of code no longer needed [WFLY-456] Fix problems from rebase, revisit security after moved WildFlySecurityManager [WFLY-456] Flesh out the syslog handler, tried with UDP [WFLY-456] Start testing the handlers and ops [WFLY-456] Set up proper syslog host and app names [WFLY-456] More tests [WFLY-456] Complete renaming appender->handler. Really [WFLY-456] Nicer separate configuration for JMX [WFLY-456] Better testing for enabled and log-read-only audit log write attribute handlers [WFLY-456] Separate handlers for JMX subsystem audit logging, and tests [WFLY-456] Maintan a failure count per appender [WFLY-456] Configure the json formatter and reference from the audit log handlers
Expose 'max-length' and 'truncate' for the syslog handler [WFLY-456] Make audit logging work in admin-only mode
Fix bug not enabling the appender in domain mode [WFLY-456] Fixes to tls syslog handler having tried it out against rsyslog [WFLY-456] don't enable log by default [WFLY-456] Test jmx audit log transformation [WFLY-456] Test audit logging in testsuite [WFLY-456] Move new i18n bits into domain-management, rather than using the ones from controller [WFLY-456] Recycle handler operation, make max-failure-count configurable per handler, expose runtime attributes for handler failure counts [WFLY-456] Use strings instead of byte for the formatters for now. We can revisit the byte part if more tamper detecting formatters are used in the future [WFLY-456] Use platform independent line terminator [WFLY-456] Changes to work with latest logmanager following a squash
Initial HTTP upgrade support for management operations This commit adds support for multiplexing the remoting protocol over the HTTP management port, removing the need for two seperate management ports.
Port 9999 is now no longer present in the default config, and the management client will attempt to connect via a HTTP upgrade by default.