Authentication & APIs
Authentication · 4 articles
Authentication not working
First, check that your authentication provider (Google, email/password, etc.) is enabled in Supabase Authentication → Providers. Then verify redirect URIs are correctly configured in Supabase Authentication → URL Configuration. Use the Cloud tab → Logs to check for specific error messages. If using Google OAuth, confirm your OAuth Client ID and Secret are correctly entered in Supabase. For complex issues, use Plan mode to investigate before retrying.
Can I add third-party APIs to my project?
Yes, use Supabase Edge Functions to securely call third-party APIs. Store API keys in Cloud → Secrets (never paste in chat). Prompt Lovable to add the integration: 'Add a feature that calls the Stripe API to get customer data.' Lovable generates the Edge Function and UI.
Ensure domain authentication is valid
For email sending, verify your domain ownership by configuring SPF, DKIM, and DMARC records as provided by Resend. These DNS records prove you control the domain and intent to send emails. Invalid or missing records cause emails to land in spam or fail delivery. Double-check record values in your DNS provider.
How do I configure authentication in Supabase?
Enable authentication in Supabase's Authentication → Providers section. Choose your methods: email/password, Google OAuth, social providers, etc. For Google OAuth, provide your OAuth Client ID and Secret from Google Cloud Console. Set redirect URLs in Supabase Authentication → URL Configuration (include localhost:3000 for dev). Lovable can auto-scaffold the sign-in UI when you ask.
