Production Auth Setup

Use this checklist before sending customers through Google sign-in on production. It prevents the confusing consent screen where Google says the user is signing in to the Supabase project host instead of ZenBid.

Required Production Values

Supabase Auth URL Configuration

In Supabase, open Authentication -> URL Configuration and set:

• Site URL: https://zenbid.ai
• Redirect URLs:
  • https://zenbid.ai/callback
  • https://zenbid.ai/auth/confirm
  • https://zenbid.ai/api/auth/callback
  • the active Render preview URL only when testing previews

Do not leave the production Site URL on an onrender.com URL or a raw Supabase project URL.

Google OAuth Branding Fix

In Google Cloud, create or select a ZenBid-owned OAuth app and set:

• App name: ZenBid
• User support email: a ZenBid support inbox
• Authorized domain: zenbid.ai
• Authorized redirect URI: https://ekocupuwjriyhtcwnqtj.supabase.co/auth/v1/callback

Then paste that Google client ID and client secret into Supabase under Authentication -> Providers -> Google.

This is the step that changes the Google consent screen from a Supabase project host to the ZenBid OAuth app. The web app cannot change that consent-screen name at runtime.

Render Environment Variables

Set these on the production web service:

NEXT_PUBLIC_SITE_URL=https://zenbid.ai
NEXT_PUBLIC_APP_URL=https://zenbid.ai
NEXT_PUBLIC_SUPABASE_URL=https://ekocupuwjriyhtcwnqtj.supabase.co

Keep NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY and SUPABASE_SECRET_KEY pointed at the same ekocupuwjriyhtcwnqtj Supabase project.

Smoke Test

1. Open https://zenbid.ai/signin in a private browser session.
2. Choose Continue with Google.
3. Confirm the Google consent screen names ZenBid, not the Supabase project host.
4. Complete sign-in and confirm the final URL is under https://zenbid.ai.
5. Confirm the user lands in /console or the requested next path.