Skip to content

Fix Gmail OAuth token exchange behind TLS proxy - #710

Merged
witbrock merged 1 commit into
mainfrom
fix/gmail-oauth-proxy-1d288b
Sep 15, 2026
Merged

witbrock merged 1 commit into
mainfrom
fix/gmail-oauth-proxy-1d288b

Conversation

@witbrock

Copy link
Copy Markdown
Member

Gmail reauthorisation behind the DGX TLS-terminating tunnel reached Google, then failed during token exchange because Flask supplied an internal HTTP callback URL. Build the authorisation response from the same configured/start-bound callback used by the OAuth flow, preserving its encoded provider query. This keeps OAuthlib HTTPS validation enabled and avoids using incoming host/forwarded headers to select the response origin.

Validated with 13 targeted OAuth service/route tests, including a new regression using OAuthlib’s real HTTPS and query parser. Existing local callback and PKCE route tests pass; formatting and diff checks pass. Live Google consent and Gmail access verification follow deployment. No scope or token-store changes.

Native Von task: #V#task_agent_730c566618d7d98ecad7fc6d263cb02c.

@witbrock
witbrock merged commit 12dce5e into main Sep 15, 2026
2 checks passed
@witbrock
witbrock deleted the fix/gmail-oauth-proxy-1d288b branch September 15, 2026 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant