Add preauthentication logging configs #9091
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Is this a bugfix, or an enhancement? Please describe.
Enhancement.
Implements a fix for #9090, as currently this logger is undocumented and difficult for someone without Log4j2 experience to figure out.
Describe the solution you've implemented
Add log4j2 configs for preauthentication to all default templates
Describe alternatives you've considered
Considered leaving it commented out, but if someone is not using the preauth module it won't make any noise. A future enhancement could be to suppress some of the logging to
DEBUGlevel instead, sinceINFOis pretty broad. That would require a code change.Additional context
#5656 has further discussion regarding how difficult it has been to debug preauthentication.