BREAKING: Supabase MINOR 🟡 signInWithIdToken failures on free tier [1kzddpb0fhwr]

Supabase experiencing partial OIDC login disruption on free-tier projects. Immediate workarounds and monitoring steps for indie hackers.

BREAKING: Supabase Sign-in Failures for OIDC Logins (Free Tier)

Status: 🟡 MINOR - Partial Disruption | Last Updated: Now | Monitoring

---

What's Down & Who's Affected

Supabase is currently experiencing sign-in failures specifically for signInWithIdToken (OIDC) authentication flows on free-tier projects only.

Direct impact:

OpenID Connect (OIDC) provider logins failing

Affects projects using Google, GitHub, Azure AD, or custom OIDC providers via token-based flow

Free-tier projects only — paid tiers appear unaffected

Auth service is partially operational; session creation is blocked for OIDC flows

Not affected:

Email/password authentication

Magic link authentication

Phone authentication

Paid tier OIDC logins (preliminary)

---

Immediate Workarounds (Do This Now)

1. Switch Authentication Method (Fastest)

Temporarily route users to email/password or magic link auth:

```javascript // Toggle OIDC visibility in your UI const useOIDC = false; // Set to false during incident

if (useOIDC) { // Show Google/GitHub buttons } else { // Show email magic link form } ```

2. Use OAuth Code Flow (If OIDC Required)

If you need social login, switch to signInWithOAuth instead:

```javascript // Instead of: await supabase.auth.signInWithIdToken({ token: idToken, provider: 'google', });

// Use: await supabase.auth.signInWithOAuth({ provider: 'google', redirectTo: window.location.origin, }); ```

3. Disable OIDC in Auth Settings

Temporarily disable affected OIDC providers in Supabase dashboard → Authentication → Providers → Toggle off problematic provider.

4. Implement Client-Side Fallback

```javascript try { const { data, error } = await supabase.auth.signInWithIdToken({ token: idToken, provider: 'google', }); if (error) throw error; } catch (err) { console.warn('OIDC failed, triggering fallback'); // Redirect to magic link or email/password form showFallbackAuth(); } ```

---

How to Check If You're Affected

1. Check your pricing tier: Dashboard → Account → Billing - Free tier = potentially affected - Pro/Team = monitor but likely unaffected

2. Test OIDC login: Try signing in with Google/GitHub on your app - If it fails with auth error → you're impacted

3. Check Supabase status page: https://status.supabase.com/ - Look for Auth service incidents

4. Monitor logs: Dashboard → Logs → Auth - Search for signInWithIdToken errors

---

Alternative Tools to Consider

If you need immediate stability and are considering alternatives:

Auth0 — robust OIDC, 7k free tier logins/month

Clerk — excellent free tier for indie hackers, OIDC-first

Firebase Authentication — stable OIDC, free tier included

NextAuth.js — self-hosted control, free

We recommend: Stay with Supabase if on paid tier. For free tier, implement workaround #2 above (OAuth flow).

---

How to Monitor Recovery

1. Subscribe to updates: - Supabase Status: https://status.supabase.com/ - Enable email notifications

2. Monitor your logs: ```bash # Check auth failures periodically curl https://your-project.supabase.co/auth/v1/health ```

3. Test periodically: - Set a reminder to test OIDC login every 15 minutes - Switch back to normal flow once successful

4. Join Discord: Supabase Discord #incidents channel for real-time updates

---

Bottom Line

This is minor and temporary. Free-tier OIDC logins are down, but authentication itself isn't broken. Use email/magic link as immediate fallback. Supabase is investigating. We'll update as recovery status changes.

Questions? Reply in comments. We're monitoring this together.