Navigation :

OPA

Enforce Open Policy Agent (OPA) policies for more fine-grained access control.

This feature is available with a Gloo Gateway license only.

If you import or export resources across workspaces, your policies might not apply. For more information, see Import and export policies.

About OPA

OPA is an open source, general-purpose policy engine that you can use to enforce versatile policies in a uniform way across your organization. Compared to a role-based access control (RBAC) authorization system, OPA allows you to create more fine-grained policies. For more information, see the OPA docs.

OPA policies are written in Rego. Based on the older query languages Prolog and Datalog, Rego extends support to more modern document models such as JSON.

Gloo Gateway's OPA integration populates an input document to use in your OPA policies. The structure of the input document depends on the context of the incoming request, described in the following table.

OPA input structure	Description
`input.check_request`	By default, all OPA policies contain an Envoy Auth Service `CheckRequest`. This object has all the information that Envoy gathers about the request being processed. You can view the structure of this object in the attributes section of the linked Envoy doc.
`input.http_request`	When processing an HTTP request, Envoy populates this field for convenience. For the structure of this object, see the Envoy `HttpRequest` docs and proto files.
`input.state.jwt`	If you use OAuth, the token retrieved during the OIDC flow is placed into this field.

The OPA external auth module can be combined with other external auth modules, such as API keys, to perform additional validation checks on incoming requests. To find an example of how to use API keys and OPA together, see API key and OPA. The following video shows an example of using OAuth and OPA.

Before you begin

This guide assumes that you use the same names for components like clusters, workspaces, and namespaces as in the getting started, and that your Kubernetes context is set to the cluster you store your Gloo config in (typically the management cluster). If you have different names, make sure to update the sample configuration files in this guide.

Follow the getting started instructions to:

Set up Gloo Gateway in a single cluster.
Deploy sample apps.
Configure an HTTP listener on your gateway and set up basic routing for the sample apps.
Make sure that the external auth service is installed and running. If not, install the external auth service in your single or multicluster environment.
```
kubectl get pods -A -l app=ext-auth-service
```

Configure an external auth policy with OPA

Create the external auth policy with OPA.

You can do the following steps in a different order, depending on when you want the policy to take effect. For example, you might want the policy to always take effect as soon as the route is created. To do so, you can create the policy before you add the route to the route table.

Create an OPA rego policy file.

cat <<EOF > policy.rego
package test
   
default allow = false
allow {
    startswith(input.http_request.path, "/ratings/2")
    input.http_request.method == "GET"
}
allow {
    input.http_request.path == "/ratings/3"
    any({input.http_request.method == "GET",
        input.http_request.method == "DELETE"
    })
}
EOF

Review the following table to understand this configuration.

Setting	Description
`default allow = false`	Denies all requests by default.
`allow {...}`	Allows requests that match two conditions as follows. 1) The path starts with `/ratings/2` AND the HTTP method is `GET`; or, 2) the path is exactly `/ratings/3` AND the HTTP method is either `GET` or `DELETE`.

Store the OPA policy in a Kubernetes config map in the workload cluster that you want to create the external auth policy in.
```
kubectl -n bookinfo create configmap allow-get-users --from-file=policy.rego
```

Create an external auth server to use for your policy.

kubectl apply -f - <<EOF
apiVersion: admin.gloo.solo.io/v2
kind: ExtAuthServer
metadata:
  name: ext-auth-server
  namespace: bookinfo
spec:
  destinationServer:
    port:
      number: 8083
    ref:
      cluster: $CLUSTER_NAME
      name: ext-auth-service
      namespace: gloo-mesh-addons
EOF

Create an external auth policy that uses the OPA config map.

When you create the policy with a destination selector, only Kubernetes services can be specified in the applyToDestination section. Gloo virtual destinations or Gloo external services are not supported.

kubectl apply -f - <<EOF
apiVersion: security.policy.gloo.solo.io/v2
kind: ExtAuthPolicy
metadata:
  name: ratings-opa
  namespace: bookinfo
spec:
  applyToRoutes:
  - route:
      labels:
        route: ratings
  config:
    server:
      name: ext-auth-server
      namespace: bookinfo
      cluster: $CLUSTER_NAME
    glooAuth:
      configs:
      - opaAuth:
          modules:
          - name: allow-get-users
            namespace: bookinfo
          query: "data.test.allow == true"
EOF

Review the following table to understand this configuration. For more information, see the API reference.

Setting	Description
`applyToRoutes`	Use labels to configure which routes to apply the policy to. This example label matches the app and route from the example route table that you previously applied. If omitted, the policy applies to all routes in the workspace.
`server`	The external auth server to use for the policy.
`opaAuth`	Configure the OPA authentication details.
`modules`	Refer to the name and namespace of the config map that has the OPA policy. Then, Gloo Gateway can use the OPA policy to use to resolve the `query`. This example uses the config map that you previously created.
`query`	The query that determines the authentication decision. The result of this query must be either a boolean or an array with a boolean as the first element. A value of `true` means that the request is authorized. Any other value or error means that the request is denied. In this example, `data.test.allow` is set to `true`. `data` is the section in the config map. `test.allow` are part of the OPA policy that you previously created. Access is allowed only if the response meets the `allow` conditions in the policy.

Verify the external auth API key policy

Send a request to the ratings app along a path that is not allowed by the OPA policy, such as /ratings/1. Now, the request is blocked with a 403 response.
- HTTP
- HTTPS
```
curl -vik --resolve www.example.com:80:${INGRESS_GW_IP} http://www.example.com:80/ratings/1
```
```
curl -vik --resolve www.example.com:443:${INGRESS_GW_IP} https://www.example.com:443/ratings/1
```

Send the request again, this time along a path that is allowed by the OPA policy, such as GET /ratings/2.

HTTP
HTTPS

curl -vik -X GET --resolve www.example.com:80:${INGRESS_GW_IP} http://www.example.com:80/ratings/2

curl -vik -X GET --resolve www.example.com:443:${INGRESS_GW_IP} https://www.example.com:443/ratings/2

You can reach the ratings app again!

{"id":1,"ratings":{"Reviewer1":5,"Reviewer2":4}}

Optional: Clean up the resources that you created.

kubectl -n bookinfo delete ConfigMap allow-get-users
kubectl -n bookinfo delete ExtAuthPolicy ratings-opa
kubectl -n bookinfo delete ExtAuthServer ext-auth-server