Docs
Social Authentication

Social Authentication

Social authentication block for Next.js

Installation

Open in

Folder structure

This block includes the Supabase client. If you already have one installed, you can skip overwriting it.

  • app
    • auth
      • error
      • login
      • oauth
    • protected
  • components
  • lib
    • supabase
1import { Card, CardContent, CardHeader, CardTitle } from '@/components/ui/card'
2
3export default async function Page({ searchParams }: { searchParams: Promise<{ error: string }> }) {
4  const params = await searchParams
5
6  return (
7    <div className="flex min-h-svh w-full items-center justify-center p-6 md:p-10">
8      <div className="w-full max-w-sm">
9        <div className="flex flex-col gap-6">
10          <Card>
11            <CardHeader>
12              <CardTitle className="text-2xl">Sorry, something went wrong.</CardTitle>
13            </CardHeader>
14            <CardContent>
15              {params?.error ? (
16                <p className="text-sm text-muted-foreground">Code error: {params.error}</p>
17              ) : (
18                <p className="text-sm text-muted-foreground">An unspecified error occurred.</p>
19              )}
20            </CardContent>
21          </Card>
22        </div>
23      </div>
24    </div>
25  )
26}

Usage

Once you install the block in your Next.js project, you'll get all the necessary pages and components to set up a social authentication flow.

Getting started

First, add a .env file to your project with the following environment variables:

NEXT_PUBLIC_SUPABASE_URL=
NEXT_PUBLIC_SUPABASE_ANON_KEY=

  • If you're using supabase.com, you can find these values in the Connect modal under App Frameworks or in your project's API settings.

  • If you're using a local instance of Supabase, you can find these values by running supabase start or supabase status (if you already have it running).

Setting up third party providers

We support a wide variety of social providers that you can use to integrate with your application. The full list is available here. This block uses the PKCE flow with GitHub as the provider. To switch providers, just update the provider field in the supabase.auth.signInWithOAuth call. Enable the provider you want to use under Auth Providers in the Supabase Dashboard and add the necessary credentials.

Setting up routes and redirect URLs

  1. Set the site URL in the URL Configuration settings in the Supabase Dashboard.
  2. Update the redirect paths in login-form.tsx to point to your app’s logged-in routes. Our examples use /protected, but you can set this to whatever fits your app.
  3. Visit http://your-site-url/auth/login to see this component in action.

Combining social auth with password-based auth

If you want to combine this block with the password-based auth, you need to:

  • Copy the handleSocialLogin function into the password-based login-form.tsx component and bind it to a "Login with ..." button.
  • Copy the @/app/auth/oauth/route.ts in your app under the same route.

Further reading