eb36716ba4
We take advantage of the JWTValidator middleware and attach it to an ingress rule based on Access configurations. We attach the Validator directly to the ingress rules because we want to take advantage of caching and token revert/handling that comes with go-oidc. |
||
|---|---|---|
| .. | ||
| middleware | ||
| config.go | ||
| config_test.go | ||
| icmp_darwin.go | ||
| icmp_darwin_test.go | ||
| icmp_generic.go | ||
| icmp_linux.go | ||
| icmp_posix.go | ||
| icmp_posix_test.go | ||
| icmp_windows.go | ||
| icmp_windows_test.go | ||
| ingress.go | ||
| ingress_test.go | ||
| origin_connection.go | ||
| origin_connection_test.go | ||
| origin_icmp_proxy.go | ||
| origin_icmp_proxy_test.go | ||
| origin_proxy.go | ||
| origin_proxy_test.go | ||
| origin_service.go | ||
| origin_udp_proxy.go | ||
| rule.go | ||
| rule_test.go | ||