fix jwt_decoder:base64_decode after breaking change in kong 3.5.0 #9
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
update to fix with kong 3.5.0
|
@telekom-digioss @Gruummy please get this in and make a 1.3.1 release thanks |
ebarped
pushed a commit
to OptareSolutions/kong-plugin-jwt-keycloak
that referenced
this pull request
Mar 18, 2024
ebarped
pushed a commit
to OptareSolutions/kong-plugin-jwt-keycloak
that referenced
this pull request
Mar 18, 2024
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.
Fix for breaking change in Kong 3.5.0 jwt_parser where they switch the from ngx.decode_base64 ngx.base64.decode_base64url and no keys were being found in jwk public keys url.