Adding client identity authentication using JWTs tokens #4
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 PR adds client identity authentication capabilities [1] by leveraging JWT Authentication mechanism provided by Envoy's filter extensions.filters.http.jwt_authn [2].
Adding matchJWT object as attribute to http rule set;
Parses applied policy containing matchJWT;
Hands over object parsed from policy to proxy xDS server (envoy API);
Adds envoy redirect with jwt_authn filter in place which listen for ingress traffic and authorize it by validating header token against policy data.
NOTE: it is necessary to enable the needed extension on envoy proxy. To enable it is necessary to uncomment the line below on proxy source file envoy_build_config/extensions_build_config.bzl, recompile the source and replace the cilium-envoy binary on system:
"envoy.filters.http.jwt_authn": "//source/extensions/filters/http/jwt_authn:config",
References:
[1] https://kloudone.atlassian.net/wiki/spaces/AC/pages/1271202197/Draft+PRD+Microsegmentation+with+Client+JWT+Identity
[2] https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/http/jwt_authn/v3/config.proto.html