Skip to content

Backport of auth/userpass: update dummy string generation into release/1.20.x#31334

Merged
mpalmi merged 1 commit into
release/1.20.xfrom
backport/update-userpass-dummy/admittedly-innocent-gibbon
Jul 18, 2025
Merged

Backport of auth/userpass: update dummy string generation into release/1.20.x#31334
mpalmi merged 1 commit into
release/1.20.xfrom
backport/update-userpass-dummy/admittedly-innocent-gibbon

Conversation

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

Backport

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

The below text is copied from the body of the original PR.


Description

Ensures the dummy string goes through the same code path as any password

TODO only if you're a HashiCorp employee

  • Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch. Note that in the CE repo, the latest release branch will look like backport/x.x.x, but older release branches will be backport/ent/x.x.x+ent.

PCI review checklist

  • I have documented a clear reason for, and description of, the change I am making.

Overview of commits

@github-actions github-actions Bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Jul 18, 2025
@mpalmi mpalmi enabled auto-merge (squash) July 18, 2025 15:15
@github-actions
Copy link
Copy Markdown

CI Results:
All Go tests succeeded! ✅

@github-actions
Copy link
Copy Markdown

Build Results:
All builds succeeded! ✅

@mpalmi mpalmi merged commit 73cd26e into release/1.20.x Jul 18, 2025
92 of 93 checks passed
@mpalmi mpalmi deleted the backport/update-userpass-dummy/admittedly-innocent-gibbon branch July 18, 2025 15:33
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 pr/no-changelog pr/no-milestone

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants