Google OAuth Credentials

Use Google OAuth Credentials to establish a secure and authenticated connection from HCL UnO Agentic AI Builder solutions to Google APIs on behalf of an end-user.

Before you begin

Ensure the following prerequisites are met:

  • You have created an OAuth 2.0 Client ID in the Google Cloud Console, under the correct project with the appropriate scopes enabled.
  • All authorized redirect URIs required by your application are registered in the OAuth client configuration in the Google Cloud Console.
Table 1. Mandatory fields
Option Description
Credential Name

A unique, user-defined name for this specific Google OAuth credential. This name will be used to identify the credential within HCL UnO Agentic AI Builder.

Client ID

The unique identifier for your Google Cloud project where the service account was created.

Client Secret The secret key associated with your Client ID, used during token exchange.
Redirect URIs-1

One or more authorized redirect URIs. These must match the URIs registered in the OAuth configuration in Google Cloud Console.

Note: You can add multiple redirect URIs using the Add URL link.
Table 2. Optional fields
Options Description
Auth Uri The URI for Google’s OAuth 2.0 authorization endpoint (e.g., https://accounts.google.com/o/oauth2/auth).
Token Uri The URI for exchanging authorization codes for access tokens (e.g., https://oauth2.googleapis.com/token).
Auth Provider X509 Cert Url URL to Google’s public certificates used to verify the OAuth provider.
Client X509 Cert Url URL to the public certificate for your OAuth client. Typically found in the client_x509_cert_url field of the credential JSON file.