Harden vote authorization flow#17
Merged
Merged
Conversation
Persist pending vote reservations across relay restarts, tighten JWT/session validation, and document the fail-closed vote flow. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Why\nHarden the relay vote path so authorization fails closed, pending reservations survive relay restarts, and sessions cannot be trusted from malformed JWTs.\n\n## What\n- Persist pending vote reservations alongside the vote registry with atomic load/save handling.\n- Tighten JWT/session validation and bind the session token to the OAuth provider claim.\n- Update the protocol and service docs to reflect the restart-safe, fail-closed vote flow.\n\n## Notes\n- No PR template was present in .github/ for this repo.\n