Google Sign-In
Use Google Sign-In for Oauth 2.0 flow and token lifecycle.
Getting Started
Google Sign-In manages the OAuth 2.0 flow and token lifecycle. To integrate the Google Sign-In workflow to your web app follow this guide.
After setting up the Google Sign-In workflow, you should have registered your
application and retrieved a Client ID. Configure your auth service
in with the Client ID.
Behavior
Authorized Invocations
When using Authorized Invocations, a tool will be considered authorized if it has a valid Oauth 2.0 token that matches the Client ID.
Authenticated Parameters
When using Authenticated Parameters, any claim provided by the id-token can be used for the parameter.
Example
authServices:
my-google-auth:
kind: google
clientId: ${YOUR_GOOGLE_CLIENT_ID}
Tip
Use environment variable replacement with the format ${ENV_NAME} instead of hardcoding your secrets into the configuration file.
Reference
| field | type | required | description |
|---|---|---|---|
| kind | string | true | Must be “google”. |
| clientId | string | true | Client ID of your application from registering your application. |