Google OAuth 2.0 Integration Guide
This guide walks you through the process of integrating Google OAuth 2.0 authentication into your JFW brand. By following these steps, you can allow your users to sign in securely using their Google accounts.
Prerequisites
A valid Google Cloud Console account with access to create OAuth credentials.
An active Admin account with permission to manage App Integrations.
Step 1: Configure Google OAuth in Google Cloud Console
Go to Google Cloud Console.
Navigate to APIs & Services > Credentials.
Click Create Credentials > OAuth client ID.
Select Web application as the application type.
Provide a name (e.g.,
BoostPTE
).Under Authorized redirect URIs, add the following URI:
https://protocol.jframework.io/api/v1/users/auth/app-integration/authenticate-urls
⚠️ This must match exactly, otherwise the authentication will fail.
Save and copy the following information:
Client ID
Client Secret
Project ID
Step 2: Configure Google Integration in Admin
Log in to your Admin.
Navigate to App Integration > Authentication.
Click Create (top-right corner).
Select Google as the provider.
Fill in the required fields:
Code – A unique code identifier for this integration.
Name – A display name for the integration.
Client ID – From Google Cloud Console.
Client Secret – From Google Cloud Console.
Project ID – From Google Cloud Console.
Scope – Define the Google OAuth scopes (e.g.,
openid profile email
).Redirect URI – Must be:
https://protocol.jframework.io/api/v1/users/auth/app-integration/authenticate-urls
Description – Optional description for internal reference.
Set Status to Active if you want to use your custom configuration immediately.
If not active, JFW will automatically fallback to the system’s default configuration.
Step 3: Authentication Flow
When a user initiates login via Google, they will be redirected to Google’s OAuth 2.0 consent screen.
Upon successful authentication, Google redirects back to:
https://protocol.jframework.io/api/v1/users/auth/app-integration/authenticate-urls
JFW processes the callback, establishes authentication, and then redirects the user to the callbackURL provided in your application via the API: Get App Integration Authenticate URLs
Last updated