WASM: Add JWT policy #30
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
This is a dirty commit POC around implementation of a policy, there are a lot of hardcoded things, and these are the reason: -> On a new filter on rust, no way to share metadata. So config should be hardcoded, PR to change that in upstream is already open. -> On JWT parsing, there is no way to get the value from Envoy, shared metadata, etc.. so need to work on decode that, all the libraries are using SSL libs, and WASM cannot be started if enabled. Signed-off-by: Eloy Coto <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #30 +/- ##
=========================================
- Coverage 0.25% 0.21% -0.04%
=========================================
Files 11 12 +1
Lines 387 455 +68
=========================================
Hits 1 1
- Misses 386 454 +68
Continue to review full report at Codecov.
|
Signed-off-by: Eloy Coto <[email protected]>
Signed-off-by: Eloy Coto <[email protected]>
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.
This is a dirty commit POC around implementation of a policy, there are a lot
of hardcoded things, and these are the reason:
-> On a new filter on rust, no way to share metadata. So config should
be hardcoded, PR to change that in upstream is already open.
-> On JWT parsing, there is no way to get the value from Envoy, shared
metadata, etc.. so need to work on decode that, all the libraries are
using SSL libs, and WASM cannot be started if enabled.
Signed-off-by: Eloy Coto [email protected]