fix(flight): accept case-insensitive authorization schemes - #1071
Open
fallintoplace wants to merge 1 commit into
Open
fix(flight): accept case-insensitive authorization schemes#1071fallintoplace wants to merge 1 commit into
fallintoplace wants to merge 1 commit into
Conversation
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.
Problem
Flight authentication compared the
BasicandBearerauthorization schemes case-sensitively, even though HTTP authentication scheme names are case-insensitive. Valid clients using forms such asbearerwere rejected.Change
Use
strings.EqualFoldfor scheme matching in both Basic and Bearer authentication paths. Credential bytes remain untouched and case-sensitive.Coverage
The regression test sends a lowercase Bearer scheme through the Flight server and verifies successful authentication.
Validation
go test ./arrow/flight