barrettruth/delta
1
0
Fork 0
Code Issues 6 Pull requests 1 Releases 3 Packages Activity Actions

feat: Google provider OAuth for Calendar and Tasks sync #290

New issue
Closed
opened 2026-05-11 18:30:38 +00:00 by barrettruth · 2 comments
barrettruth commented 2026-05-11 18:30:38 +00:00
Owner
Copy link

Problem

Google Calendar sync and Google Tasks pull both need a working Google provider connection, but that must not become app login again.

The owner should connect one Google account from a self-hosted single-user Delta instance. The OAuth redirect URI must match the deployed app origin and be documented clearly enough that the operator can configure Google Cloud without guessing.

Solution

  • Add or repair the Google provider OAuth connect/callback flow for integrations.
  • Keep this separate from app authentication and sessions.
  • Store access/refresh tokens through the encrypted integration settings path.
  • Document required Google Cloud project setup, redirect URI, client ID/secret env names, and scopes.
  • Include the scopes needed by Calendar sync (#123) and Tasks pull (#291).
  • Surface redirect/provider errors in settings instead of failing silently.

Acceptance criteria

  • A self-hosted instance can connect and disconnect one Google account from settings.
  • The documented redirect URI matches the actual route used by the app.
  • Tokens are not exposed in logs, issues, docs, PR descriptions, or client-rendered output.
  • #123 and #291 build on this provider connection without creating their own auth flows.
## Problem Google Calendar sync and Google Tasks pull both need a working Google provider connection, but that must not become app login again. The owner should connect one Google account from a self-hosted single-user Delta instance. The OAuth redirect URI must match the deployed app origin and be documented clearly enough that the operator can configure Google Cloud without guessing. ## Solution - Add or repair the Google provider OAuth connect/callback flow for integrations. - Keep this separate from app authentication and sessions. - Store access/refresh tokens through the encrypted integration settings path. - Document required Google Cloud project setup, redirect URI, client ID/secret env names, and scopes. - Include the scopes needed by Calendar sync (#123) and Tasks pull (#291). - Surface redirect/provider errors in settings instead of failing silently. ## Acceptance criteria - A self-hosted instance can connect and disconnect one Google account from settings. - The documented redirect URI matches the actual route used by the app. - Tokens are not exposed in logs, issues, docs, PR descriptions, or client-rendered output. - #123 and #291 build on this provider connection without creating their own auth flows.
barrettruth added this to the v0.1.0 milestone 2026-05-11 18:30:38 +00:00
barrettruth commented 2026-05-11 21:02:45 +00:00
Author
Owner
Copy link

Foundation dependency note: #355 should land or be deliberately trimmed before this starts, especially #356 and #357 so Google provider OAuth builds on one provider registry and server-owned provider mutation path.

Foundation dependency note: #355 should land or be deliberately trimmed before this starts, especially #356 and #357 so Google provider OAuth builds on one provider registry and server-owned provider mutation path.
barrettruth commented 2026-05-14 04:13:23 +00:00
Author
Owner
Copy link

Completed by the current Google provider sync path and merged read-only stack: Settings can connect/disconnect one Google account through /api/integrations/google, tokens use encrypted integration config storage, docs cover redirect URI/env/scopes, and Google Tasks/Calendar now build on this provider connection without separate auth flows.

Completed by the current Google provider sync path and merged read-only stack: Settings can connect/disconnect one Google account through /api/integrations/google, tokens use encrypted integration config storage, docs cover redirect URI/env/scopes, and Google Tasks/Calendar now build on this provider connection without separate auth flows.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feat/software-sync
ship/delta-codex-skill
fix/cli-filter-args
fix-calendar-g-leader-shortcuts
harden-keyboard-capture
fix-queue-gc-hard-refresh
fix/task-panel-scroll-restoration
fix/calendar-quick-add-preview-stability
fix/467-local-first-shortcuts
docs/nixos-self-hosting-first-pass
calendar-elapsed-events
calendar-active-day-blue
calendar-outline-no-fill
calendar-neutral-day-state
fix-calendar-drag-visual-position
issue-364-task-api-route-adapters
issue-362-manpage-drift
issue-315-geocoding-config
release/cli-0.0.5
release/cli-0.0.4
fix/task-panel-save-atomicity
settings-modal
feat/add-task-external-links
feat/reminder-transport-settings
feat/reminder-foundation
build/oidc-release-pipeline
fix/settings-cleanup
fix/remove-oauth-config-ui
cli-v0.0.6
cli-v0.0.5
cli-v0.0.4
nightly-20260426
cli-v0.0.2
Labels
Clear labels   
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
status:blocked
Blocked on a decision, credential, or external dependency

  
track:api
API layer track

  
track:auto
Automation track

  
track:core
Core engine track

  
track:deploy
Deployment track

  
track:infra
Infrastructure track

  
track:ui
Web UI track

  
type:cleanup
Small cleanup, polish, or consolidation work

  
type:docs
Documentation and operator guidance

  
type:epic
Umbrella issue that coordinates related work

  
type:release
Release, packaging, and versioning work

  
type:research
Decision or investigation work before implementation

  
wontfix
This will not be worked on

No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
status:blocked
track:api
track:auto
track:core
track:deploy
track:infra
track:ui
type:cleanup
type:docs
type:epic
type:release
type:research
wontfix
Milestone
Clear milestone
No items
No milestone
v0.1.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
barrettruth/delta#290
No description provided.