Documentation

Authentication

Ignitra uses Supabase Auth with multiple sign-in methods.

Supported Methods

  • Email + Password
  • Magic Link (passwordless email)
  • Google OAuth
  • GitHub OAuth

Setting Up Google OAuth

  1. Go to Google Cloud Console → APIs & Services → Credentials
  2. Create an OAuth 2.0 Client ID
  3. Set authorized redirect URI: https://your-supabase-url.supabase.co/auth/v1/callback
  4. Copy the Client ID and Client Secret
  5. In Supabase Dashboard → Authentication → Providers → Google
  6. Enable Google and paste the credentials

Setting Up GitHub OAuth

  1. Go to GitHub → Settings → Developer Settings → OAuth Apps
  2. Create a new OAuth app
  3. Set authorization callback URL: https://your-supabase-url.supabase.co/auth/v1/callback
  4. Copy the Client ID and Client Secret
  5. In Supabase Dashboard → Authentication → Providers → GitHub
  6. Enable GitHub and paste the credentials

Row Level Security (RLS)

Every database table has RLS policies enabled. Users can only access their own data. This is enforced at the database level — not just application code — making it impossible to access another user's data even if there's a bug in your API routes.

Authentication | Ignitra Docs