Use a custom JWKS endpoint for discoveryv3.14+

Set a custom JWKS endpoint for the OpenID Connect plugin to use instead of the one returned by the internal discovery mechanism. This is useful when the IdP exposes a non-standard JWKS endpoint.

This option is similar to extra_jwks_uris, but it overrides the endpoint instead of providing multiple fallback options. If you need to use multiple JWKS endpoints, see the Token validation for multiple IdPs example.

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

  • JWKS_ENDPOINT: The URL of the JWKS endpoint to use instead of the jwks_uri returned by the internal discovery mechanism.

  • TOKEN_SALT: A random string that decK requires (v1.59 and later) so session credentials aren’t regenerated on every sync. This parameter is optional for other formats. For example, generate one with openssl rand -base64 16.

Set up the plugin

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!