fix: pass whitelabel project logo to OAuth redirect page

@zen-agentchecks n/achecks…zen/fix-whitelabel-redirect-logo-my1pae → master2 files · +24 −2review: @rohanprabhureview: @sohamganatrareview: @sarthakreview: @acsrujanreview: @kaavee315review: @lingalarahul7review: @anshugarg15updated 3w ago

GitHub

▸Description· 1 comment · 6 noise

Description

Fix white-labeling issue where the OAuth success/redirect page (/redirect?status=success) always shows the default Composio logo instead of the customer's configured whitelabel logo.

Root cause: The OAuth callback handler (handleAuthCallback) did not include the project's custom logo URL when constructing the redirect URL. The redirect page at platform.composio.dev/redirect had no way to know about the whitelabel configuration.

Fix (backend side):

Added config: true to the project select in handleAuthCallback to fetch the project configuration
Parse ProjectConfigSchema to extract logoURL from the project config
Added appLogo field to the CallbackResult interface
Pass appLogo as a query parameter in the redirect URL when present

Companion frontend PR: ComposioHQ/frontend — reads the appLogo query param and displays it via AppIcon instead of the hardcoded Logo component.

Ticket: T-11225 Triggered by: palash@composio.dev | Source: slack Session: https://zen-api-production-4c98.up.railway.app/dashboard/#/chat/zen-64c28838f6cf

How did I test this PR

Ran vitest run src/lib/connected_accounts/handleOAuthCallback.test.ts — 7 passed
Ran vitest run src/pages/api/v3/toolkits/auth/callback.test.ts — 1 passed
Verified Apollo health check passes (curl localhost:9900/api/healthz)
Frontend lint passes with 0 errors
TypeScript compilation clean for changed files

@zen-agent3w ago

Post-PR Status Update

Codex Review

Verdict: LGTM — No issues found. Codex confirmed the changes consistently propagate the optional project logo from validated project config into the OAuth callback redirect without affecting existing success or failure handling.

CI Status

29/30 checks passed
run-vitest-e2e-tests failed on first run due to an unrelated timeout in rerouted/v1/triggers/index.test.e2e.ts — re-run triggered, awaiting result
The same test passes on master — this is a flaky timeout, not caused by this PR

Build Checks

pnpm lint ✅
pnpm format:check ✅
pnpm check-types ✅

Tests Executed

handleOAuthCallback.test.ts — 7/7 passed
callback.test.ts — 1/1 passed
E2E runtime check: Apollo callback route returns 302 correctly

PR Comments

No human review comments to address (only bot comments: Vercel, Codecov, reviewer suggestions)

▸ 6 bot/status comments hidden

@vercel[bot]3w ago

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
apollo	Ready	Preview, Comment	May 20, 2026 7:12pm

Project	Deployment	Actions	Updated (UTC)
debby	Skipped		May 20, 2026 7:12pm

@github-actions[bot]3w ago

🔍 Suggested Reviewers

Based on git blame analysis of 2 file(s):

Contributor	Contribution	Files
lingalarahul7	38%	2
jkomyno

loading diff…

Flag	Coverage Δ
e2e-tests	`6.03% <0.00%> (-0.01%)`	:arrow_down:
self-hosted-tests	`5.58% <0.00%> (-0.01%)`	:arrow_down:
unit-tests	`58.93% <88.23%> (-0.01%)`	:arrow_down:

Files with missing lines	Coverage Δ
.../src/lib/connected_accounts/handleOAuthCallback.ts	`69.45% <100.00%> (+0.33%)`	:arrow_up:
.../apollo/src/pages/api/v3/toolkits/auth/callback.ts	`92.10% <81.81%> (-0.91%)`	:arrow_down:

fix: pass whitelabel project logo to OAuth redirect page

Description

How did I test this PR

Post-PR Status Update

Codex Review

CI Status

Build Checks

Tests Executed

PR Comments

🔍 Suggested Reviewers

Description

How did I test this PR

Post-PR Status Update

Codex Review

CI Status

Build Checks

Tests Executed

PR Comments

🔍 Suggested Reviewers

💡 Recommendation

🧪 Test Results Summary (Self-Hosted Tests)

Codecov Report

🧪 Test Results Summary (Unit Tests)

🧪 Test Results Summary (E2E Tests)