This page covers how to write policies for the content of the requests that are passed to OPA by Envoy’s External Authorization filter.

Writing Policies

Let’s start with an example policy that restricts access to an endpoint based on a user’s role and permissions.

package envoy.authz
import input.attributes.request.http
default allow = false
allow {
    is_token_valid
    action_allowed
}
is_token_valid {
  token.valid
  now := time.now_ns() / 1000000000
  token.payload.nbf <= now
  now < token.payload.exp
}
action_allowed {
  http.method == "GET"
  token.payload.role == "guest"
  glob.match("/people/*", ["/"], http.path)
}
action_allowed {
  http.method == "GET"
  token.payload.role == "admin"
  glob.match("/people/*", ["/"], http.path)
}
action_allowed {
  http.method == "POST"
  token.payload.role == "admin"
  glob.match("/people", ["/"], http.path)
  lower(input.parsed_body.firstname) != base64url.decode(token.payload.sub)
}
token := {"valid": valid, "payload": payload} {
    [_, encoded] := split(http.headers.authorization, " ")
    [valid, _, payload] := io.jwt.decode_verify(encoded, {"secret": "secret"})
}

The first line package envoy.authz declaration gives the (hierarchical) name envoy.authz to the rules in the remainder of the policy. If the OPA-Envoy configuration does not specify the path field, envoy/authz/allow will be considered as the default policy decision path. data.envoy.authz.allow will be the name of the policy decision to query in the default case.

The above policy uses the io.jwt.decode_verify builtin function to parse and verify the JWT containing information about the user making the request. It uses other builtins like glob.match, lower, base64url.decode etc. OPA has 150+ builtins detailed at openpolicyagent.org/docs/policy-reference.

The dot notation seen in multiple places in the policy for ex. input.parsed_body.firstname simply descends through the hierarchy to access the requested value. The dot (.) operator never throws any errors; if the path does not exist the value of the expression is undefined.

data.envoy.authz.allow

Sample input received by OPA is shown below:

{
  "attributes": {
    "request": {
      "http": {
        "method": "GET",
        "path": "/people/",
        "headers": {
          "authorization": "Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJyb2xlIjoiZ3Vlc3QiLCJzdWIiOiJZV3hwWTJVPSIsIm5iZiI6MTUxNDg1MTEzOSwiZXhwIjoxNjQxMDgxNTM5fQ.K5DnnbbIOspRbpCr2IKXE9cPVatGOCBrBQobQmBmaeU"
        }
      }
    }
  }
}

With the input value above, the answer is:

false

Example Policy with Object Response

The allow rule in the above policy returns a boolean decision to indicate whether a request should be allowed or not. If you’d like your rule to not only indicate if a request is allowed or not but also provide optional response headers, body and HTTP status that can be sent to the downstream client or upstream, the below allow rule generates an object that provides additional details along with the status of the request (ie. allowed or denied).

package envoy.authz
default allow = {
  "allowed": false,
  "headers": {"x-ext-auth-allow": "no"},
  "body": "Unauthorized Request",
  "http_status": 301
}
allow = response {
  input.attributes.request.http.method == "GET"
  response := {
    "allowed": true,
    "headers": {"x-ext-auth-allow": "yes"}
  }
}

data.envoy.authz.allow

Sample input received by OPA is shown below:

{
  "attributes": {
    "request": {
      "http": {
        "method": "GET",
        "path": "/people",
        "headers": {
          "authorization": "Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJyb2xlIjoiZ3Vlc3QiLCJzdWIiOiJZV3hwWTJVPSIsIm5iZiI6MTUxNDg1MTEzOSwiZXhwIjoxNjQxMDgxNTM5fQ.K5DnnbbIOspRbpCr2IKXE9cPVatGOCBrBQobQmBmaeU"
        }
      }
    }
  }
}

With the input value above, the answer is:

{
  "allowed": true,
  "headers": {
    "x-ext-auth-allow": "yes"
  }
}

Input Document

In OPA, input is a reserved, global variable whose value is the request sent by the Envoy External Authorization filter to OPA. The OPA-Envoy plugin supports both v2 and v3 versions of the CheckRequest which is used to pass the request to OPA.

For v3 requests, the specified JSON mapping for protobuf is used for making the incoming envoy.service.auth.v3.CheckRequest available in input. It differs from the encoding used for v2 requests. In v3, all keys are lower camelcase. Also, needless nesting of oneof values is removed.

For example, source address data that looks like this in v2,

"source": {
  "address": {
    "Address": {
      "SocketAddress": {
        "PortSpecifier": {
          "PortValue": 59052
        },
        "address": "127.0.0.1"
      }
    }
  }
}

becomes, in v3,

"source": {
  "address": {
    "socketAddress": {
      "address": "127.0.0.1",
      "portValue": 59052
    }
  }
}

The following table shows the rego code for common data, in v2 and v3:

Due to those differences, it’s important to know which version is used when writing policies. Thus, this information is passed into the OPA evaluation under input.version, where you’ll either find, for v2,

input.version == { "ext_authz": "v2", "encoding": "encoding/json" }

or, for v3,

input.version == { "ext_authz": "v3", "encoding": "protojson" }

To have Envoy use the v3 version of the service, the http_filters entry in the Envoy configuration should look like below (minimal version):

http_filters:
- name: envoy.ext_authz
  typed_config:
    '@type': type.googleapis.com/envoy.extensions.filters.http.ext_authz.v3.ExtAuthz
    transport_api_version: V3
    grpc_service:
      google_grpc: # or envoy_grpc
        target_uri: "127.0.0.1:9191"

Example Input

Example v3 Input ```json { “attributes”: { “source”: { “address”: { “socketAddress”: { “address”: “172.17.0.1”, “portValue”: 61402 } } }, “destination”: { “address”: { “socketAddress”: { “address”: “172.17.06”, “portValue”: 8000 } } }, “request”: { “time”: “2020-11-20T09:47:47.722473Z”, “http”: { “id”:”13519049518330544501”, “method”: “POST”, “headers”: { “:authority”:”192.168.99.206:30164”, “:method”:”POST”, “:path”:”/people?lang=en”, “accept”: “*/*“, “authorization”:”Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJyb2xlIjoiYWRtaW4iLCJzdWIiOiJZbTlpIiwibmJmIjoxNTE0ODUxMTM5LCJleHAiOjE2NDEwODE1Mzl9.WCxNAveAVAdRCmkpIObOTaSd0AJRECY2Ch2Qdic3kU8”, “content-length”:”41”, “content-type”:”application/json”, “user-agent”:”curl/7.54.0”, “x-forwarded-proto”:”http”, “x-request-id”:”7bca5c86-bf55-432c-b212-8c0f1dc999ec” }, “host”:”192.168.99.206:30164”, “path”:”/people?lang=en”, “protocol”:”HTTP/1.1”, “body”:”{\“firstname\“:\“Charlie\“, \“lastname\“:\“Opa\“}”, “size”:41 } }, “metadataContext”: {} }, “parsed_body”:{“firstname”: “Charlie”, “lastname”: “Opa”}, “parsed_path”:[“people”], “parsed_query”: {“lang”: [“en”]}, “truncated_body”: false, “version”: { “encoding”:”protojson”, “ext_authz”:”v3” } } ``` Example v2 Input ```json { “attributes”:{ “source”:{ “address”:{ “Address”:{ “SocketAddress”:{ “PortSpecifier”:{ “PortValue”:61402 }, “address”:”172.17.0.1” } } } }, “destination”:{ “address”:{ “Address”:{ “SocketAddress”:{ “PortSpecifier”:{ “PortValue”:8000 }, “address”:”172.17.0.6” } } } }, “request”:{ “http”:{ “id”:”13519049518330544501”, “method”:”POST”, “headers”:{ “:authority”:”192.168.99.206:30164”, “:method”:”POST”, “:path”:”/people?lang=en”, “accept”:”*/*“, “authorization”:”Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJyb2xlIjoiYWRtaW4iLCJzdWIiOiJZbTlpIiwibmJmIjoxNTE0ODUxMTM5LCJleHAiOjE2NDEwODE1Mzl9.WCxNAveAVAdRCmkpIObOTaSd0AJRECY2Ch2Qdic3kU8”, “content-length”:”41”, “content-type”:”application/json”, “user-agent”:”curl/7.54.0”, “x-forwarded-proto”:”http”, “x-request-id”:”7bca5c86-bf55-432c-b212-8c0f1dc999ec” }, “host”:”192.168.99.206:30164”, “path”:”/people?lang=en”, “protocol”:”HTTP/1.1”, “body”:”{\“firstname\“:\“Charlie\“, \“lastname\“:\“Opa\“}”, “size”:41 } } }, “parsed_body”:{“firstname”: “Charlie”, “lastname”: “Opa”}, “parsed_path”:[“people”], “parsed_query”: {“lang”: [“en”]}, “truncated_body”: false, “version”: { “encoding”:”encoding/json”, “ext_authz”:”v2” } } ```

The parsed_path field in the input is generated from the path field in the HTTP request which is included in the Envoy External Authorization CheckRequest message type. This field provides the request path as a string array which can help policy authors perform pattern matching on the HTTP request path. The below sample policy allows anyone to access the path /people.

package envoy.authz
default allow = false
allow {
   input.parsed_path = ["people"]
}

The parsed_query field in the input is also generated from the path field in the HTTP request. This field provides the HTTP URL query as a map of string array. The below sample policy allows anyone to access the path /people?lang=en&id=1&id=2.

package envoy.authz
default allow = false
allow {
   input.parsed_path = ["people"]
   input.parsed_query.lang = ["en"]
   input.parsed_query.id = ["1", "2"]
}

The parsed_body field in the input is generated from the body field in the HTTP request which is included in the Envoy External Authorization CheckRequest message type. This field contains the deserialized JSON request body which can then be used in a policy as shown below.

package envoy.authz
default allow = false
allow {
   input.parsed_body.firstname == "Charlie"
   input.parsed_body.lastname == "Opa"
}

The truncated_body field in the input represents if the HTTP request body is truncated. The body is considered to be truncated, if the value of the Content-Length header exceeds the size of the request body.

Example with JWT payload passed from Envoy

Envoy can be configured to pass validated JWT payload data into the ext_authz filter with metadata_context_namespaces and payload_in_metadata.

Example Envoy Configuration

http_filters:
- name: envoy.filters.http.jwt_authn
  typed_config:
  "@type": type.googleapis.com/envoy.config.filter.http.jwt_authn.v2alpha.JwtAuthentication
  providers:
    example:
      payload_in_metadata: verified_jwt
      <...>
- name: envoy.ext_authz
  config:
    metadata_context_namespaces:
    - envoy.filters.http.jwt_authn
    <...>

Example OPA Input

This will result in something like the following dictionary being added to input.attributes (some common fields have been excluded for brevity):

  "metadata_context": {
    "filter_metadata": {
      "envoy.filters.http.jwt_authn": {
        "verified_jwt": {
          "email": "alice@example.com",
          "exp": 1569026124,
          "name": "Alice"
        }
      }
    }
  }