OpenID Connect with Googlev1.0+

Authenticate browser clients using Google’s identity provider.

Prerequisites

  • A Gateway Service and Route secured with HTTPS.

  • Set up a Google API project and create a set of OAuth client ID credentials with the Web application class.

  • An authorized redirect URI for the part of the API you want to protect.

Environment variables

  • ISSUER: The issuer authentication URL for your IdP. For Google, that typically looks like this: https://accounts.google.com/.well-known/openid-configuration

  • 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 Google.

  • REDIRECT_URI: The authorized redirect URI that you created in the Cloud Console, which determines where Google sends responses to your authentication requests.

  • 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!