Google OAuth login does not persist provider connection state required by downstream integrations

[Ridanshi]

Summary

Google OAuth authentication succeeds but does not persist provider connection metadata in the same way as other integrations.

As a result, downstream functionality relying on provider connection state cannot consistently identify Google-linked accounts.

Affected Files

• auth.ts
• connect.ts

Root Cause

The Google login flow authenticates users successfully but does not persist equivalent provider metadata expected by downstream integration logic.

This creates inconsistencies between provider types.

Reproduction

1. Authenticate using Google OAuth.
2. Inspect provider connection records.
3. Compare with GitHub-connected accounts.
4. Observe missing or inconsistent connection state.

Expected Behavior

All OAuth providers should persist equivalent integration metadata.

Actual Behavior

Google-authenticated users can lack expected provider linkage information.

Why This Is Difficult To Detect

Authentication itself succeeds.

The issue only appears when integration-aware features are exercised.

Production Impact

• Inconsistent provider behavior
• Broken downstream features
• Integration confusion
• Hard-to-debug account state

Suggested Fix

Persist provider metadata consistently across all OAuth providers.

Severity

Medium-High

[Ridanshi]

I investigated this issue and would like to work on it.

The current Google OAuth flow appears to authenticate successfully while leaving downstream provider state inconsistent.

I plan to:

• review provider persistence behavior
• align provider metadata handling across authentication flows
• preserve existing login behavior
• add regression coverage for provider-linked accounts

Please assign this issue to me.

[VIDYANKSHINI]

Hi @Harxhit,

I've looked into the authentication and provider linkage flow in auth.ts and connect.ts. The issue seems to be that while the user is authenticated via Google, the corresponding provider connection metadata (oAuthToken / linkage state) isn't being upserted consistently compared to other integrations.

I can fix this by ensuring the provider metadata is properly persisted upon successful Google authentication, and I will also add the necessary regression tests to prevent this from happening in the future.

Could you please assign this issue to me?

[Harxhit]

@VIDYANKSHINI I have assigned this issue to you.