feat(hoocloak): allow default password for users without hash - #16
Merged
Merged
Conversation
wakemeup0
added a commit
that referenced
this pull request
Sep 29, 2026
Publish Hoocloak 2.1.0 after the successful CI run for main commit 6f871f8. - Bump the provider and Helm chart versions to 2.1.0. - Add changelog entries including the default-password behavior from #16. - Compatibility/security impact: users without `password_hash` can sign in with the shared password `hoo`; configured hashes remain authoritative. Operators requiring individual credentials must set hashes for all users. - Deployment: release artifacts are built and published by the protected release workflow after this PR merges and the release commit passes CI. - Rollback: deploy the prior image/chart version; configs with omitted hashes must first restore valid hashes for that version. Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
wakemeup0
added a commit
that referenced
this pull request
Sep 29, 2026
Complete the prepared Hoocloak 2.1.0 release after the release workflow failed on the protected main branch. The failed run attempted to rewrite `main` and create `v2.2.0`, which repository rules rejected. This change tags the already reviewed release commit after its main CI succeeds, verifies the tag points to that commit, and feeds the existing image, chart, and GitHub Release jobs. It also accepts GitHub's squash-merge PR suffix for a release commit and for a manual publication retry. - Compatibility: no change to Hoocloak runtime behavior beyond #16. - Security: the default `hoo` password remains limited to users without a configured hash, as documented in #16. Tag creation still requires successful CI on the exact release commit. - Deployment: merge with the PR title shown here so the existing release workflow recognizes the release commit. - Rollback: no runtime rollback is needed for this CI-only change; the `v2.1.0` tag is checked for commit identity and never moved. Validation: Bash subject matching was checked for exact, PR-suffixed, and incorrect versions; `git diff --check` passed. The full GitHub CI remains the release gate.
This file contains hidden or 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
1 participant
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.
Change
password_hashand authenticate them withhoo.Closes #15.
Compatibility and security
Deployment and rollback
Validation
go test -tags no_otel ./...passed locally using Go 1.26.4 in Docker.git diff --checkpassed.