Update jwt_verify_lib to 2020-02-11 #10228
Merged
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
Signed-off-by: Wayne Zhang <qiwzhang@google.com>
|
@lizan could you help to merge this change? Thanks |
|
/azp run envoy-macos |
|
Commenter does not have sufficient privileges for PR 10228 in repo envoyproxy/envoy |
|
/azp run envoy-macos |
|
Commenter does not have sufficient privileges for PR 10228 in repo envoyproxy/envoy |
|
master and CI is locked now for security release, will merge after. |
mattklein123
approved these changes
Mar 3, 2020
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.
Signed-off-by: Wayne Zhang qiwzhang@google.com
Description:
Jwt_verify_lib added PEM public key type support. But Envoy jwt_authn http filter only uses JWKS type. It is not using PEM type. This PR just updates its SHA to the latest, did not bring any essential changes .
Risk Level: Low
Testing: Unit-test
Docs Changes: None
Release Notes: None
[Optional Fixes #Issue]
[Optional Deprecated:]