Skip to content

Replace deprecated OOB OAuth flow with localhost redirect#42

Merged
a-bonus merged 1 commit intoa-bonus:mainfrom
concord-consortium:fix-oauth-deprecated-oob-redirect
Feb 10, 2026
Merged

Replace deprecated OOB OAuth flow with localhost redirect#42
a-bonus merged 1 commit intoa-bonus:mainfrom
concord-consortium:fix-oauth-deprecated-oob-redirect

Conversation

@scytacki
Copy link
Copy Markdown
Contributor

@scytacki scytacki commented Feb 9, 2026

Summary

  • Google deprecated the urn:ietf:wg:oauth:2.0:oob redirect URI, causing "Access blocked" errors when authorizing new Desktop-type OAuth clients
  • Replaces the manual copy-paste authorization flow with a temporary local HTTP server on 127.0.0.1 that catches the OAuth callback automatically
  • The server uses a random available port, which Google allows by default for Desktop OAuth clients without requiring explicit redirect URI configuration

Test plan

  • Delete existing token.json and re-run authorization with a Desktop-type OAuth client
  • Verify the browser opens the consent screen and redirects back to localhost
  • Verify token.json is created with a valid refresh token
  • Verify the MCP server starts and connects successfully after authorization

🤖 Generated with Claude Code

Google deprecated the `urn:ietf:wg:oauth:2.0:oob` redirect URI,
causing "Access blocked" errors for new OAuth clients. This replaces
the manual copy-paste flow with a temporary local HTTP server that
catches the OAuth callback automatically.

The server listens on a random port on 127.0.0.1, which Google
allows by default for Desktop-type OAuth clients without requiring
explicit redirect URI configuration.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@a-bonus a-bonus merged commit eea0d50 into a-bonus:main Feb 10, 2026
@scytacki scytacki deleted the fix-oauth-deprecated-oob-redirect branch February 12, 2026 14:59
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.

2 participants