0Pricing
Supabase Backend as a Service · Lesson

Social Logins (OAuth Providers)

Integrate popular OAuth providers like Google, GitHub, or Facebook to offer seamless social login experiences for your users.

Social Logins (OAuth Providers) is a free Supabase Backend as a Service lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Supabase Backend as a Service learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Simplify Sign-Ups with Social Logins

Tired of users creating new passwords for every app? Social logins, also known as OAuth providers, let users sign in with their existing accounts from services like Google, GitHub, or Facebook.

This makes signing up much faster and more convenient, improving the user experience and potentially increasing user adoption.

Supabase Makes OAuth Easy

Supabase acts as a powerful intermediary, simplifying the complex OAuth flow. Instead of you writing intricate logic for each provider, Supabase handles the redirects, token exchanges, and session management securely.

This means you can integrate multiple social login options with minimal code.

Activate Providers in Your Project

Before writing any code, you need to enable the desired social login providers in your Supabase project dashboard.

  • Go to Authentication > Providers.
  • Toggle on providers like Google, GitHub, or Facebook.
  • You'll need to configure their respective Client ID and Client Secret, obtained from the provider's developer console.

The `signInWithOAuth` Method

The core of initiating a social login in your application is the Supabase JavaScript client's signInWithOAuth() method. This function redirects your user to the chosen provider's login page.

It takes a provider name (e.g., 'google', 'github') and an optional options object, typically including a redirectTo URL.

Initiate Google Login

Here's a practical example of how to start a Google login flow. When this code runs, the user will be sent to Google's authentication page.

Remember to replace window.location.origin + '/auth/callback' with your actual callback URL.

import { createClient } from '@supabase/supabase-js';

// Initialize Supabase client (replace with your actual URL and Anon Key)
const supabaseUrl = 'YOUR_SUPABASE_URL';
const supabaseAnonKey = 'YOUR_SUPABASE_ANON_KEY';
const supabase = createClient(supabaseUrl, supabaseAnonKey);

async function signInWithGoogle() {
  const { data, error } = await supabase.auth.signInWithOAuth({
    provider: 'google',
    options: {
      redirectTo: window.location.origin + '/auth/callback'
    }
  });

  if (error) {
    console.error('Error initiating Google login:', error.message);
  } else {
    console.log('Redirecting to Google for authentication...');
    // User will be redirected automatically
  }
}

// To run this, you'd typically call signInWithGoogle()
// on a button click event in a web application.
// For example: signInWithGoogle();

The OAuth Redirect Flow

After the user successfully logs in with the social provider (e.g., Google), the provider redirects them back to your application.

This redirect includes special parameters in the URL that Supabase uses to establish the user's session securely. It's a critical part of the OAuth process.

Handling the Callback Route

Your application needs a designated callback route (e.g., /auth/callback) to receive the redirect from the OAuth provider.

The Supabase client library automatically listens for these URL parameters on page load and processes them to create a user session. You typically don't need to write explicit code for this route beyond initializing the Supabase client.

Accessing User Session Data

Once authenticated via social login, Supabase provides access to the user's session and profile information. You can use methods like supabase.auth.getSession() to retrieve the active session details.

The session object contains the user's ID, email, and other metadata provided by the OAuth provider.

Check the Current Session

This example shows how to check if a user is currently logged in and retrieve their session data. This is often done after the callback redirect or on app startup.

import { createClient } from '@supabase/supabase-js';

// Initialize Supabase client (replace with your actual URL and Anon Key)
const supabaseUrl = 'YOUR_SUPABASE_URL';
const supabaseAnonKey = 'YOUR_SUPABASE_ANON_KEY';
const supabase = createClient(supabaseUrl, supabaseAnonKey);

async function getCurrentUserSession() {
  const { data: { session }, error } = await supabase.auth.getSession();

  if (error) {
    console.error('Error getting session:', error.message);
    return null;
  }

  if (session) {
    console.log('User is logged in!');
    console.log('User ID:', session.user.id);
    console.log('Email:', session.user.email);
    console.log('Provider:', session.user.app_metadata.provider);
    return session;
  } else {
    console.log('No active session.');
    return null;
  }
}

// Call this function to check the session
// getCurrentUserSession();

Keep Your App Secure

Security is paramount with authentication:

  • Use HTTPS: Always ensure your application is served over HTTPS.
  • Valid `redirectTo` URLs: Configure your redirectTo URLs carefully in both Supabase and the OAuth provider's settings to prevent redirect attacks.
  • Client-Side Keys: Never expose your Supabase Service Role Key on the client-side; only use the Anon Key for client-side operations.

Social Login Check

When using supabase.auth.signInWithOAuth(), what is the primary purpose of the redirectTo option?

Recap & Next Steps

You've successfully learned how to integrate social logins using Supabase! This powerful feature simplifies user authentication, enhances convenience, and leverages existing user accounts from popular OAuth providers like Google and GitHub.

You now understand the role of signInWithOAuth(), the redirect flow, and how to retrieve user session data.

Next, explore how to manage user sessions and profiles, including updating user metadata and handling logout functionalities securely.

Frequently asked questions

Is the “Social Logins (OAuth Providers)” lesson free?

Yes — the full text of “Social Logins (OAuth Providers)” is free to read here on the web, and the Supabase Backend as a Service course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Supabase Backend as a Service course, upgrade to CoddyKit PRO.

What will I learn in “Social Logins (OAuth Providers)”?

Integrate popular OAuth providers like Google, GitHub, or Facebook to offer seamless social login experiences for your users. You practise Supabase Backend as a Service with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Supabase Backend as a Service?

No prior experience is required. Supabase Backend as a Service on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Social Logins (OAuth Providers)” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Supabase Backend as a Service lesson?

Yes. Every Supabase Backend as a Service lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

  1. User Registration with Email/Password
  2. Social Logins (OAuth Providers)
  3. Managing User Sessions & Profiles
  4. Password Reset and Magic Link Authentication
← Back to Supabase Backend as a Service