Preliminary Checks
Reproduction
A minimal reproduction link has not been provided. Steps to reproduce are included below.
Publishable key
Not provided.
Description
I found this while reconnecting a disconnected Google One Tap account in UserProfile with Google OAuth configured. After clicking Reconnect and completing session reverification, the request sent strategy=google_one_tap and failed with:
Google_one_tap OAuth provider not enabled.
Steps to reproduce:
- Configure Google OAuth.
- Open UserProfile for a user with a disconnected Google account originally connected through Google One Tap.
- Click Reconnect for that account.
- Complete session reverification.
- Observe the failed request using
strategy=google_one_tap.
Expected behavior:
Reconnect starts regular Google OAuth using strategy=oauth_google, preserving session reverification.
Actual behavior:
Reconnect sends strategy=google_one_tap, resulting in the provider-not-enabled error even though Google OAuth is configured.
Cause and proposed fix:
ConnectedAccountsSection reuses account.verification.strategy when calling user.createExternalAccount(). For Google One Tap accounts, that value is google_one_tap, which cannot be reused to start the OAuth reconnect flow.
Normalize google_one_tap to oauth_google for reconnect while preserving the existing reverification flow. Add regression coverage verifying that both the initial request and the retry after reverification use oauth_google.
Environment
Affected application environment details and SDK versions have not been provided.
Preliminary Checks
Reproduction
A minimal reproduction link has not been provided. Steps to reproduce are included below.
Publishable key
Not provided.
Description
I found this while reconnecting a disconnected Google One Tap account in UserProfile with Google OAuth configured. After clicking Reconnect and completing session reverification, the request sent
strategy=google_one_tapand failed with:Steps to reproduce:
strategy=google_one_tap.Expected behavior:
Reconnect starts regular Google OAuth using
strategy=oauth_google, preserving session reverification.Actual behavior:
Reconnect sends
strategy=google_one_tap, resulting in the provider-not-enabled error even though Google OAuth is configured.Cause and proposed fix:
ConnectedAccountsSectionreusesaccount.verification.strategywhen callinguser.createExternalAccount(). For Google One Tap accounts, that value isgoogle_one_tap, which cannot be reused to start the OAuth reconnect flow.Normalize
google_one_taptooauth_googlefor reconnect while preserving the existing reverification flow. Add regression coverage verifying that both the initial request and the retry after reverification useoauth_google.Environment
Affected application environment details and SDK versions have not been provided.