We currently document the library mode audit logger tool, need to add the client server tool
Tristan, could you share your thoughts on the queries posted in Comment 5
CS issue resolved. All the changes reflected.
Vojtech indicated there are other methods of configuring audit logger in server mode. He is going to delve into it and provide the other config or setup info by today or tomorrow. Bug on hold as awaiting further data.
As I wrote, audit log is ignored in server mode - i.e. this part of doc is wrong and needs to be removed.
Hey Tristan, Vojtech's finding reveals that the audit logger is ignored in the server mode and the provided config doesn't cause any parse errors (i.e. is correct), but doesn't log any security events.
Vojtech suggested removing the server config (remove after consulting with developers) by providing a brief explanation on why the audit log is ignored as customers would expect it to be available in server mode also. So please offer your comments on this to steer this bug devel further.
I'm sorry, it actually works correctly, but the security has to be turned on also on the cache:
<local-cache name="default" start="EAGER">
<locking isolation="NONE" acquire-timeout="30000" concurrency-level="1000" striping="false"/>
<authorization roles="admin reader writer supervisor"/>
I got confused by provided config sample or didn't realize it for some reason when I test it. With conf sniplet provided above the audit logger in server mode works correctly.
Thank you Vojtech for your time and attention! Appreciate it! NP with the confusion, its all part of our game. What matters is the end sweet result! :-)
This content is now available on https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Data_Grid/