ACL plugin authorization

Configure the OpenID Connect plugin for ACL-based authorization.

This example uses password authentication, but you can use any supported authentication type with ACL groups.

For a full example that shows you how to set up both the OpenID Connect and ACL plugins with Keycloak as the IdP, see Configure OpenID Connect with ACL authorization.

Note: Setting config.client_auth to client_secret_post lets you easily test the connection to your IdP, but we recommend using a more secure auth method in production. You can use any of the supported client auth methods.

Prerequisites

  • A configured identity provider (IdP)

  • An ACL plugin configured with allow or deny lists

Environment variables

  • ISSUER: The issuer authentication URL for your IdP. For example, if you’re using Keycloak as your IdP, the issuer URL looks like this: http://localhost:8080/realms/example-realm

  • CLIENT_ID: The client ID that the plugin uses when it calls authenticated endpoints of the IdP.

  • CLIENT_SECRET: The client secret needed to connect to your IdP.

Set up the plugin

Something wrong?

Help us make these docs great!

Kong Developer docs are open source. If you find these useful and want to make them better, contribute today!