Google Social Login Integration Guide

Step 1: Obtain Client ID and Client Secret

• Log in to Google Cloud Console and create an OAuth 2.0 application. Google will generate a Client ID and Client Secret.

• Here’s how to proceed with the process:

A. Sign in to Google Cloud Console - Go to: https://console.cloud.google.com - Log in using your Google account. B. Create or Select a Project - Click the project dropdown in the top bar. - Choose an existing project or click "New Project". - Enter a project name and (optionally) organization. - Click Create. - After creation, make sure your project is selected.

C: Enable Required APIs - In the left sidebar, go to APIs & Services > Library. - Search for and enable the Google People API (for user profile info) - Click Enable. D: Set Up OAuth Consent Screen - Go to APIs & Services > OAuth consent screen - Choose "External". - Click Create. - Fill in App Info: App Name (e.g., JobSphere Admin Tool), User Support Email, App Logo (optional), Developer Contact Info, Add Scopes (optional). - Click Save and Continue until you finish.

E: Create OAuth 2.0 Client ID - Go to APIs & Services > Credentials - Click + Create Credentials > OAuth Client ID - Choose Application Type: For web apps, select Web Application. For other types (Android, iOS, etc.), select accordingly. - Fill in the Name and Authorized Redirected URL. - Click Create.

F: Get Client ID and Secret - Once created, Google will show: Client ID and Client Secret. - Click Download or copy them to configure your app.

• Important: The client must share these credentials with the Artha Support Team, who will add them to the backend. The client does not need to configure or add them anywhere.

• Ensure that the callback/redirect URL is set correctly in the Google Cloud Console: https://api.arthajobboard.com/social-auth/google/callback

• Google requires verification for certain applications. The client must wait for Google’s approval before the login can be configured.

Step 2: Verify Application Settings

• Ensure Correct Branding:

  • The application name, logo, and other branding settings should reflect the client’s identity.

• Confirm Redirect URL:

  • The redirect URL configured in Google Cloud Console should match the one provided above.

Step 3: Testing & Confirmation

• The Client must wait for confirmation from Artha Support before testing.

• Google approval may take time— only after approval can the integration be configured. This process might take a few weeks. It depends on Google to approve.

• Perform login tests to ensure smooth user authentication and correct branding.

• Check for Artha Branding: Ensure no references to Artha (e.g., logos, names) appear.

Step 4: Deployment & Monitoring

• Once confirmed, the social login will be active.

• Monitor login success rates via analytics or server logs.

• Regularly review credentials and rotate the Client Secret as per security best practices.