Skip to content

Comments

fix: require GOOGLE_PUBSUB_VERIFICATION_TOKEN for webhook security#1

Merged
don4of4 merged 3 commits intomainfrom
claude/analyze-repo-issues-p8oh9
Dec 28, 2025
Merged

fix: require GOOGLE_PUBSUB_VERIFICATION_TOKEN for webhook security#1
don4of4 merged 3 commits intomainfrom
claude/analyze-repo-issues-p8oh9

Conversation

@don4of4
Copy link
Owner

@don4of4 don4of4 commented Dec 27, 2025

Previously, if GOOGLE_PUBSUB_VERIFICATION_TOKEN was not set, the webhook
would accept all requests without verification. This change rejects
requests when the token is not configured, preventing unauthenticated
webhook abuse.

Previously, if GOOGLE_PUBSUB_VERIFICATION_TOKEN was not set, the webhook
would accept all requests without verification. This change rejects
requests when the token is not configured, preventing unauthenticated
webhook abuse.
The getProgressMessage function was refactored to use completedThreadIds
from state instead of a remainingCount parameter. Updated tests to:
- Remove the unused second parameter
- Set up completedThreadIds in test state
Changed `prompt: "consent"` to `prompt: "select_account"` in three places:
- Main Google OAuth config (auth.ts)
- Google account linking (linking/auth-url/route.ts)
- Google calendar auth (calendar/auth-url/route.ts)

Previously, the consent screen was shown on every login even when no new
permissions were requested. Now it only shows when permissions change.
@don4of4 don4of4 merged commit 0538acc into main Dec 28, 2025
1 check passed
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