RFC 7804 - SCRAM Authentication Implementation with SHA-256 - #2154
Merged
hyperxpro merged 4 commits intoMar 21, 2026
Merged
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
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.
Motivation:
Add SCRAM-SHA-256 HTTP authentication (RFC 7804) — mutual password-based auth with PBKDF2 key derivation that never transmits the password over the wire.
Modification:
Add SCRAM_SHA_256 to AuthScheme, ScramEngine for crypto (PBKDF2, HMAC-SHA-256, RFC 7613 password normalization), ScramContext for per-exchange state, ScramSessionCache for reauthentication, and ScramMessageParser/ScramMessageFormatter for RFC 5802 wire format.
Result:
Added RFC 7804 SCRAM-SHA-256 support