Skip to content

Latest commit

 

History

History
56 lines (40 loc) · 2.82 KB

README.md

File metadata and controls

56 lines (40 loc) · 2.82 KB
Raw

OPA Istio External Authorization proof of concept

This is a small proof of concept project with some OPA policy for validating requests to multiple apps in an istio cluster.

opa-envoy-plugin provides a GRPC service implementing the Envoy ext_authz protocol. Istio can be configured with external authorization to validate (and modify) requests using this server. One instance of OPA is deployed (a sidecar configuration is not used) in this example.

./test.sh

or

istioctl operator init
kubectl apply -f istiooperator.yaml
# Wait for Istio to come up, then:
kustomize build . | kubectl create -f -

Tested with Istio 1.10.1 and OPA 0.29.1-envoy.

NOTE: OPA is configured without any authentication in this example.

  • Centralized OPA instance with modular policy structure allowing different policy for each app
    • Policy is selected based on destination Istio principal (SPIFFE URL including namespace and service account)
  • JWT static secret validation
  • JWT validation using JWKS HTTP endpoint

Header manipulation

See plugins["envoy_ext_authz_grpc"].path docs at: https://www.openpolicyagent.org/docs/latest/envoy-introduction/ for the syntax on the allow { ... } rules. If the response is an object with a headers value, they will be sent upstream when allowed: true. This allows replacing an authorization header (or any other header) before sending it upstream. It is not possible to remove the Authorization header with the fields that opa-envoy-plugin provides (allowed_upstream_headers from ext_authz can't be configured with opa-envoy-plugin).

It is possible for OPA to accept a JWT, enforce poicy and then swap the credentials for something else before sending them onto an upstream application. This allows putting complex policy validation in front of an application that may not even JWTs at all. The one risk to avoid is that the upstream application MUST NOT ever send the final credentials back to the downstream user.

sequenceDiagram
    Client->>App Sidecar: JWT
    activate App Sidecar
    Note over App Sidecar, OPA-Envoy: OPA External Authorization (ext_authz)
    activate App Sidecar
    App Sidecar->>+OPA-Envoy: JWT
    OPA-Envoy->>-App Sidecar: App service account credentials
    deactivate App Sidecar
    App Sidecar->>+App API: App service account credentials
    App API->>-Client: API response
    deactivate App Sidecar
Loading

See also