User info authentication

Configure the OpenID Connect plugin to use user info authentication.

In this example, the OpenID Connect plugin will only accept bearer tokens sent in a header, but you can also set the bearer_token_param_type parameter to body, query, or any combination of these values.

For a complete example of authenticating with a token retrieved through Keycloak’s user info endpoint, see the tutorial for configuring OpenID Connect with user info.

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)

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!