Description
Description
This RFE is about adding more details when the admin-event is logged by the JBossLoggingEventListenerProvider .
The possible suggestion is to:
-
Doublecheck that in case that adminEvent contains some
details(FieldAdminEvent.details), those details are logged by the JBoss-logging listener to the server.log. It seems that it already works like that based on the commit 0a05ba49 , but it will be good to doublecheck. -
Possibility to optionally log the representation for the admin events. In case that event has representation, it can be good to have some option to log the representation to the server.log. This will need to be explicitly enabled by the SPI switch during server startup. Maybe with something like this:
./kc.sh start --spi-events-listener-jboss-logging-enable-representation=true
It should be disabled by default as the field "representation" could be very big (especially for some cases like for example updating realm) . We should document that it should be used with care due to the big representation. Also there is a risk that some sensitive data might be leaked from the representation in the server.log, so we should maybe document this risk. In case that event-store is doing some sanitization of some representation fields, the jboss-logging implementation should make this sanitization as well.
Discussion
No response
Motivation
No response
Details
No response