not check typ in jwt header #36
Open
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
KayEss
reviewed
Jul 8, 2020
| @@ -152,10 +152,6 @@ fostlib::nullable<fostlib::jwt::token> fostlib::jwt::token::load( | |||
| const auto u8_header = coerce<utf8_string>(v64_header); | |||
| const auto str_header = coerce<string>(u8_header); | |||
| const auto header = json::parse(str_header); | |||
| if (header["typ"] != jwt) { | |||
| log::warning(c_fost)("", "JWT type mismatch")("typ", header["typ"]); | |||
| return fostlib::null; | |||
There was a problem hiding this comment.
Can we leave the warning, but just remove the early return? I think it's clear it's meant to be there and I'd rather the code looks like it's not missed something
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.
No description provided.