Awesome

Kong plugin kong-authz-openfga

The goal of this plugin is to integrate Kong with OpenFGA for fine-grained authorization. It allows you to define and enforce access control policies using OpenFGA.

Installation

Install the plugin using luarocks. @TODO: The package is not yet hosted on LuaRocks or as an release asset on GitHub.

luarocks install kong-plugin-kong-authz-openfga-0.1.0-1.all.rock

Enable it in Kong

https://docs.konghq.com/gateway/3.9.x/reference/configuration/#plugins

Capabilities

• Integrates with OpenFGA for authorization
• Supports Lua expressions for dynamic policy evaluation

Limitations

• No caching support yet

Example minimal configuration

Below is the minimal example configuration one might use in declarative_config:

- name: kong-authz-openfga
  config:
    host: localhost
    port: 1234
    store_id: "your_store_id"
    tuple:
      user: "user_id"
      relation: "relation"
      object: "object_id"

Example full configuration

Below is the example configuration one might use in declarative_config:

- name: kong-authz-openfga
  config:
    host: localhost
    port: 1234
    https: true
    https_verify: true
    timeout: 10000
    keepalive: 60000
    store_id: "your_store_id"
    model_id: "your_model_id"
    api_token: "your_api_token"
    api_token_issuer: "your_api_token_issuer"
    api_audience: "your_api_audience"
    api_client_id: "your_api_client_id"
    api_client_secret: "your_api_client_secret"
    api_token_cache: 600
    tuple:
      user: "user_id"
      relation: "relation"
      object: "object_id"
    contextual_tuples:
      - user: "user_id"
        relation: "relation"
        object: "object_id"

Configuration

Plugin version

Version: 0.1.0

Plugin priority

Priority: 901

Plugin handler phases

Handler phases:

• access

Local development

For local development, building and testing a containerized environment is used. The containerized environment is defined in the Makefile. For the unit and integration test the busted framework is used. To test Kong the spec helper from the kong-pongo toolkit is bundled in the project.

Prerequisites for local development

• git
• make (download it from https://sourceforge.net/projects/ezwinports/files/make-4.4-without-guile-w32-bin.zip/download)
• bash
• Docker
• A text editor

Initial setup

For the initial setup of the local development environment, the following steps are required:

1. Copy the file .env.tpl to .env and adjust the values to your needs.
2. Docker is running and is able to pull images from docker.io.
3. make is installed

Run lint, unit and integration tests

To run the lint, unit and integration tests just execute make. This will all run all tests in a containerized environment.

make

Lint

Check linting and general Lua programming errors with make lint

make lint

Run test

make test-unit

Pack the plugin into a .rock

make pack

Format code

Format the code with make format-code

make format-code

Inspect logs from test runs

Run each command in a separate terminal. Align the terminal side-by-side for a better overall view.

You might want to prefix the make tail-logs commands with winpty for better signal/abort handling.

Tail the kong logs.

make tail-logs

Run the tests.

make test-unit

Run the tests with a BUSTED_FILTER and don't continue on the first failure.

make test-unit BUSTED_FILTER="test case name" BUSTED_NO_KEEP_GOING=1

For further debugging the Kong working directory is mounted to your local ./servroot folder. The working directory contains Kong configuration, logs and additional settings.<br><br> 🚨 For each test case the Kong working directory is wiped. Just use a combination of BUSTED_FILTER and BUSTED_NO_KEEP_GOING to get a faster feedback loop.

Run a smoke test

Make sure to populate all the environment variables in the .env file. The smoke test will use the values from the .env file.

In order to run the smoke test two terminal windows are required. In the first terminal window run the following command:

make smoke-test-run-server

In the second terminal window run the following command:

make smoke-test-run-test

The logs from the smoke test are visible in the first terminal window.

Clean local development

It's recommended to clean the local development after a new git fetch&rebase/pull.

make clean

Run CI lint, unit and integration tests

@TODO: Add build, test, and deploy pipeline (GitHub Actions) to the project

Test against a different Kong version

To test the plugin against a different Kong version change the KONG_VERSION and the KONG_IMAGE_HASH in the plugin.properties file.

Behind the scene

The local development environment is inspired by the kong-pongo toolkit. The spec helper from kong-pongo is bundled in the project. All the linting and test are running in a containerized environment that is based on the _build/images/kong-tooling/Dockerfile. This image could also be reused for CI.

Similar to the tooling image the smoke test run in a different containerized environment that is based on the _build/images/kong-smoke-test/Dockerfile. The smoke test uses the Kong configuration and script from _build/deployment/kong-smoke-test. The smoke test container emulates a Kong environment that installs a .rocks (Luarocks package) file.

Mock service

The project bundles a mock server for OpenFGA.

Mock service in Lua

@TODO: TBD

CI container image

@TODO: TBD

Recommended Visual Studio Code extensions

• https://marketplace.visualstudio.com/items?itemName=sumneko.lua
• https://marketplace.visualstudio.com/items?itemName=dwenegar.vscode-luacheck

Release a new version

1. Checkout the main branch
   1. git checkout main
2. Update the version number in plugin.properties
3. Update the version number in kong-plugin.rockspec
4. Update the version number in README.md
5. Update the version number in kong/plugins/kong-authz-openfga/handler.lua
6. Add a new section to CHANGELOG.md with the release highlights
7. Commit the changes, create a tag and push changes and tag to the remote repository
   1. git add plugin.properties kong-plugin.rockspec README.md kong/plugins/*/handler.lua CHANGELOG.md
   2. git commit -m "Release x.y.z-r"
   3. git tag x.y.z-r
   4. git push
   5. git push --tags
8. @TODO: Add step to publish the *.rock file to LuaRocks
9. @TODO: Add step to perform a release in GitHub