Batch 7.0: Fix Zoho OAuth Token Endpoint Bug #74
Labels
No Label
P0 Critical
P1 High
P2 Medium
P3 Low
accessibility
backend
bug
content
data-integrity
enhancement
frontend
infra
integration
owner
owner-input
performance
performance
phase-7
phase-8
security
seo
ui
ux
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: null/Queue-North-Website#74
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Batch 7.0 — Fix Zoho OAuth Token Endpoint Bug
Phase: 7 — Zoho CRM Integration
Agent: Neo (backend)
Priority: P1 High — critical bug, Zoho integration will fail in production without this
Problem
The refresh token POST currently goes to
{ZOHO_API_DOMAIN}/oauth/v2/tokenbut Zoho requires the token endpoint to be on the accounts server (accounts.zoho.comfor US,accounts.zoho.eufor EU), NOT the API domain (www.zohoapis.com). This is a bug that will prevent token refresh from working.Tasks
ZOHO_ACCOUNTS_DOMAINenv var (default:https://accounts.zoho.com)getZohoAccessToken()to use accounts domain, not API domainredirect_urifrom refresh token request.env.examplewith new env varZOHO_ENABLED=falsefirst (verify no regressions)Files to modify
server/index.js— Token endpoint fix, remove redirect_uri, add retryDockerfile— Add ZOHO_ACCOUNTS_DOMAIN env var.env.example— Add ZOHO_ACCOUNTS_DOMAINAcceptance criteria
ZOHO_ACCOUNTS_DOMAIN, notZOHO_API_DOMAINredirect_uriin refresh token request bodyZOHO_ENABLED=false