Add concept overview for Google suite hub#1
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| 1. Redirect the user to Google's OAuth URL with scopes: | ||
| - `https://www.googleapis.com/auth/gmail.readonly` | ||
| - `https://www.googleapis.com/auth/tasks.readonly` | ||
| - `https://www.googleapis.com/auth/calendar.readonly` | ||
| 2. Exchange the authorization code for access + refresh tokens. |
There was a problem hiding this comment.
Request offline consent before expecting refresh tokens
The minimal OAuth flow instructs calling Google’s authorization URL with only the three API scopes (lines 31‑34) yet step 2 assumes the code exchange will yield refresh tokens. For Google web apps, a refresh token is only issued when the initial authorize request includes offline consent parameters (e.g., access_type=offline and, after first grant, prompt=consent); otherwise you only receive a short‑lived access token and the later persistence/refresh logic cannot work. Please add the offline consent flags to the authorize step so refresh tokens are reliably returned.
Useful? React with 👍 / 👎.
Summary
Testing
Codex Task