[All] Correcting Bearer Authorization header #698
Merged
Conversation
This file contains 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
|
Thanks for submitting your first pull request! You are awesome! 🤗 |
manics
reviewed
Nov 20, 2023
There was a problem hiding this comment.
Other than the comment this seems reasonable.
@GeorgianaElena what do you think?
Closed
|
Congrats on your first merged pull request in this project! 🎉 |
4 tasks
|
Thank you @yaleman and thank you @jyio for the amazing resaerch in #677 (comment) - wow!! ❤️ 🎉 🌻 |
consideRatio
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently the value for the "Authorization" header is taken from the case-insensitive "token_type" field (RFC 6750) sent by the OAuth IDP. This PR corrects for this and matches the RFC 6749 requirement of having title-cased "Bearer".
References: #677 and #676