Rei Shimizu
**What this PR does / why we need it**: Draft of AuthN wasm implementation. **Which issue this PR fixes** To resolve https://github.com/istio/istio/issues/15772 **Special notes for your reviewer**: We can't build...
**What this PR does / why we need it**: This is a part of replacement of authn wasm implementation. It is using revised request authentication API. https://github.com/istio/api/pull/1536 #2800 is too...
This is a part of replacement of authn wasm implementation. It is using revised peer authentication API. istio/api#1536 istio#2800 is too large and hard to review all codes so that...
Related with https://github.com/envoyproxy/envoy-wasm/pull/476. We require to retrieve TLS certificate information via wasm VM. As written, there are two approaches. In my opinion, we should add `enum WasmMapType` and include `TlsPeerCertificate`...
Signed-off-by: Shikugawa
Previous HTTP client code has some problems. 1. It doesn't have transport socket options. So we can't switch raw or tls socket to use in requesting. 2. Many lines of...
This is related with https://github.com/istio-ecosystem/authservice/issues/140 The current filter chain matches by prefix or equality, but matching by regular expression will make the rules more expressive. For example, a use case...
This is a necessary feature to realize #172: by introducing the and/or/not semantics into the filter chain match, we can integrate the features that currently realize TriggerRule into Matcher. For...
TriggerRule and FilterChain matcher have overlapping functionality; TriggerRule currently uses only path attributes to determine whether to match or not. However, this can be achieved by specifying `:path` in the...