Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of Implement user lockout log into release/1.14.x #23587

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #23140 to be assessed for backporting due to the inclusion of the label backport/1.14.x.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@davidadeleon
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/vault/merges: 409 Merge conflict []

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_interval parameter.

Example Config:
user_lockout_log_interval="30s"


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/davidadeleon/implement-user-lockout-log/loosely-many-cardinal branch from 3fdc2db to 590a97a Compare October 10, 2023 16:00
@hashicorp-cla
Copy link

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes


temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

Have you signed the CLA already but the status is still pending? Recheck it.

@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Oct 10, 2023
@github-actions
Copy link

CI Results:
Failures:

Test Type Package Test Logs
builtin/logical/database TestBackend_StaticRole_LockRegression view test results

@davidadeleon
Copy link
Contributor

Backported here: #23630

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants