Skip to content
This repository has been archived by the owner on May 7, 2020. It is now read-only.

Investigate sending Wildfly/Keycloak audit logs to stdout #194

Open
hkeeler opened this issue Dec 1, 2017 · 2 comments
Open

Investigate sending Wildfly/Keycloak audit logs to stdout #194

hkeeler opened this issue Dec 1, 2017 · 2 comments

Comments

@hkeeler
Copy link
Member

hkeeler commented Dec 1, 2017

As mentioned on #193 (comment), it'd be nice to the the Keycloak's Wildfly audit logs going to stdout like the rest of the logs. As it stands now, they all go to file, and thus trapped in the container.

hkeeler added a commit to hkeeler/hmda-platform-auth that referenced this issue Dec 1, 2017
@hkeeler
Copy link
Member Author

hkeeler commented Jan 8, 2018

I think I have this figured out. Keycloak already does log all login events, however, non-error events are being logged at DEBUG, but rootLogger is at INFO. We have a couple options:

We could just bump the rootLogger to DEBUG, but that'd likely bring in a bunch of other DEBUB-level logs we're not interested in, and it'd likely involve further logging config to get it turned jus right.

A better way seems to be to override the default eventListener with something like:

<spi name="eventsListener">
  <provider name="jboss-logging" enabled="true">
    <properties>
      <property name="success-level" value="INFO"/>
      <property name="error-level" value="WARN"/>
    </properties>
  </provider>
</spi>

Check out the following for further details on Keycloak's event listener:

@hkeeler
Copy link
Member Author

hkeeler commented Jan 17, 2018

This issue is less critical than #210. I'm swapping these two issues in the 1.21.0 release.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant