Overview

DreamOS86 uses Supabase Auth for all authentication, including OAuth providers. The platform supports Google and GitHub sign-in out of the box.

Setting up Google OAuth

1. Create a Google Cloud project

14px] text-muted-foreground">Go to [Google Cloud Console

Create a new project or select an existing one

Navigate to APIs & Services → Credentials

2. Create OAuth credentials

Click Create Credentials → OAuth client ID

Select Web application

Add your authorised redirect URIs:

- http://localhost:3000/auth/callback (development)

- https://yourdomain.com/auth/callback (production)

- Add the Supabase callback too: https://your-project.supabase.co/auth/v1/callback

3. Configure Supabase

14px] text-muted-foreground">Go to your [Supabase project dashboard

Auth → Providers → Google

Enable Google, paste your Client ID and Client Secret

4. Add redirect URLs to Supabase

Auth → URL Configuration → Redirect URLs:

http://localhost:3000/auth/callback

https://dreamos86.com/auth/callback

---

Setting up GitHub OAuth

1. Create a GitHub OAuth App

14px] text-muted-foreground">Go to [GitHub Developer Settings

Click OAuth Apps → New OAuth App

Set:

- Homepage URL: https://dreamos86.com

- Authorization callback URL: https://your-project.supabase.co/auth/v1/callback

2. Configure Supabase

Auth → Providers → GitHub

Enable GitHub, paste your Client ID and Client Secret

3. Add redirect URLs

Same as Google — add both localhost and production URLs to Supabase's allowed redirect list.

---

Testing OAuth locally

Google and GitHub OAuth both work on localhost:3000 as long as:

http://localhost:3000/auth/callback is in your Supabase redirect URLs

The Google Cloud credentials have http://localhost:3000/auth/callback as an authorised URI

Your NEXT_PUBLIC_APP_URL=http://localhost:3000 in .env.local

Troubleshooting

"Provider not enabled"

→ The provider hasn't been enabled in Supabase Auth settings.

"Redirect URI mismatch"

→ The URL your app is redirecting to doesn't match exactly what's registered in Google Console or Supabase. Check for trailing slashes.

"callback_failed" error after OAuth

→ Usually a network error or SSL certificate issue in local development. The src/instrumentation.ts file in your project automatically handles SSL certificate issues on Windows in development.

Session not persisting after OAuth login

→ Ensure your middleware is refreshing the session on every request and that cookies are being set correctly.