Backport of Implement user lockout log into release/1.15.x #23588
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
github-actions
bot
added
the
hashicorp-contributed-pr
|
Build Results: |
|
CI Results: |
schavis
added
the
vault-update
…er-lockout-log/normally-smart-mackerel
…er-lockout-log/normally-smart-mackerel
davidadeleon
approved these changes
Oct 11, 2023
davidadeleon
deleted the
backport/davidadeleon/implement-user-lockout-log/normally-smart-mackerel
branch
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.
Backport
This PR is auto-generated from #23140 to be assessed for backporting due to the inclusion of the label backport/1.15.x.
The below text is copied from the body of the original PR.
This PR adds a log which will be emitted at a configurable interval (default of 1 minute), in the event of there being a locked user anywhere in Vault. This adds visibility for operators around the user lockout feature via the operational logs, allowing them to know when a user lockout is in effect. A WARN log will be emitted when a lockout is in effect, and an INFO log will be emitted when all lockouts have been cleared. The log interval can be modified as part of the server config using the
user_lockout_log_intervalparameter.Example Config:
user_lockout_log_interval="30s"Overview of commits