feat: add DB-backed encrypted Google OAuth token storage - #9
Open
Mustafa-Esoofally wants to merge 9 commits into
Open
feat: add DB-backed encrypted Google OAuth token storage#9Mustafa-Esoofally wants to merge 9 commits into
Mustafa-Esoofally wants to merge 9 commits into
Conversation
- Add shared AuthConfig for Gmail + Calendar providers (scope consolidation) - Store OAuth tokens in PostgreSQL with Fernet encryption - Check DB tokens before falling back to file-based tokens - Add migration script to move existing file tokens to DB - Requires GOOGLE_TOKEN_ENCRYPTION_KEY env var for encryption Co-Authored-By: Claude <noreply@anthropic.com>
…rage - Extract provider factories to agents/providers/ (google, slack, core, hardening) - Slim agents/sources.py to registry + tool hardening only - Shared AuthConfig for Gmail + Calendar with pre-registered scopes - DB + encryption as the only path (no file fallback complexity) - Simplified google_mint_tokens.py with --generate-key option - Remove migrate_google_tokens_to_db.py (just re-auth instead) - Bump agno to 2.6.20
Mints encrypted Google OAuth tokens directly to Railway DB. Creates TCP proxy via Railway GraphQL API if needed. Usage: python scripts/railway/google_auth.py [--force]
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
AuthConfigfor Gmail + Calendar providers (scope consolidation)Why
Addresses the Google auth pain point mentioned by Ashpreet - no more juggling multiple token files. Single OAuth consent covers all Google services, tokens encrypted and stored in the same DB as everything else.
Setup
Requires
GOOGLE_TOKEN_ENCRYPTION_KEYenv var for encryption:Migration
Test plan
Dependencies
Requires agno PR with
auth=param for context providers (feat/google-context-providers-auth)🤖 Generated with Claude Code