Justin Bertram ecead9b130 ARTEMIS-2974 audit logger can print wrong user info ... Using a ThreadLocal for the audit user information works in most cases, but it can fail when dispatching messages to consumers because threads are taken out of a pool to do the dispatching and those threads may not be associated with the proper credentials. This commit fixes that problem with the following changes: - Passes the Subject explicitly when logging audit info during dispatch - Relocates security audit logging from the SecurityManager implementation(s) to the SecurityStore implementation - Associates the Subject with the connection properly with the new security caching		2020-11-05 11:38:08 -05:00
..
logging-CI.properties	ARTEMIS-2732 Cleanup on testsuite logging	2020-04-22 23:08:46 -04:00
logging.properties	ARTEMIS-2974 audit logger can print wrong user info	2020-11-05 11:38:08 -05:00
logging.properties.trace	ARTEMIS-612 Improving Failback's max replication	2016-07-05 16:51:23 -05:00
server-start-stop-backup-config1.xml	renamed schemas	2015-04-29 10:49:43 +01:00
server-start-stop-backup-jms-config1.xml	NO-JIRA Clean up xml files	2016-07-06 17:16:16 -04:00
server-start-stop-live-config1.xml	renamed schemas	2015-04-29 10:49:43 +01:00
server-start-stop-live-jms-config1.xml	renamed schemas	2015-04-29 10:49:43 +01:00