Skip to content

Fix Drive OAuth client path to live server endpoint - #39

Merged
sandervonk merged 1 commit into
mainfrom
cursor/fix-drive-oauth-path-361d
Sep 8, 2026
Merged

sandervonk merged 1 commit into
mainfrom
cursor/fix-drive-oauth-path-361d

Conversation

@sandervonk

Copy link
Copy Markdown
Member

Summary

The Portal TaskWorkspace "Connect Drive" flow was calling a non-existent client path (POST /api/v1/oauth/drive/start) and falling back to a stub that showed a warning toast instead of opening OAuth.

This updates the client to match the live mvtt-server route:

  • POST /api/v1/me/drive/oauth/start
  • Uses { url, state } from the response and opens url in a new tab

Changes

  • startDriveOAuth() in src/common/workspace.ts — correct endpoint, require url in response
  • TaskWorkspace.vue connectDrive() — always open returned URL; remove stub toast and fake driveConnected state

Notes

Server-side GOOGLE_OAUTH_CLIENT_ID / SECRET may still be placeholders; this is the required client-side path fix so Connect Drive reaches the real OAuth flow when credentials are configured.

Open in Web Open in Cursor 

Update startDriveOAuth to POST /api/v1/me/drive/oauth/start and open
the returned url. Remove the stub fallback and warning toast so Connect
Drive opens the real OAuth redirect.

Co-authored-by: Sander Vonk <sandervonk@users.noreply.github.com>
@sandervonk
sandervonk marked this pull request as ready for review September 8, 2026 20:16
@sandervonk
sandervonk merged commit 059d16f into main Sep 8, 2026
1 check passed
@sandervonk
sandervonk deleted the cursor/fix-drive-oauth-path-361d branch September 8, 2026 20:16
sandervonk added a commit to cmu-tt/cmu-tt.github.io that referenced this pull request Sep 8, 2026
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