Auth

Login with Discord


To enable Discord Auth for your project, you need to set up a Discord Application and add the Application OAuth credentials to your Supabase Dashboard.

Overview

Setting up Discord logins for your application consists of 3 parts:

Access your Discord account

  • Go to discord.com.
  • Click on Login at the top right to log in.

Discord Portal.

Discord Portal.

Find your callback URL

The next step requires a callback URL, which looks like this: https://<project-ref>.supabase.co/auth/v1/callback

  • Go to your Supabase Project Dashboard
  • Click on the Authentication icon in the left sidebar
  • Click on Providers under the Configuration section
  • Click on Discord from the accordion list to expand and you'll find your Callback URL, you can click Copy to copy it to the clipboard

Create a Discord application

  • Click on New Application at the top right.
  • Enter the name of your application and click Create.
  • Click on OAuth2 under Settings in the left side panel.
  • Click Add Redirect under Redirects.
  • Type or paste your callback URL into the Redirects box.
  • Click Save Changes at the bottom.
  • Copy your Client ID and Client Secret under Client information.

Add your Discord credentials into your Supabase project

  • Go to your Supabase Project Dashboard
  • In the left sidebar, click the Authentication icon (near the top)
  • Click on Providers under the Configuration section
  • Click on Discord from the accordion list to expand and turn Discord Enabled to ON
  • Enter your Discord Client ID and Discord Client Secret saved in the previous step
  • Click Save

Add login code to your client app

When your user signs in, call signInWithOAuth() with discord as the provider:

1
2
3
4
5
async function signInWithDiscord() { const { data, error } = await supabase.auth.signInWithOAuth({ provider: 'discord', })}

For a PKCE flow, for example in Server-Side Auth, you need an extra step to handle the code exchange. When calling signInWithOAuth, provide a redirectTo URL which points to a callback route. This redirect URL should be added to your redirect allow list.

In the browser, signInWithOAuth automatically redirects to the OAuth provider's authentication endpoint, which then redirects to your endpoint.

1
2
3
4
5
6
await supabase.auth.signInWithOAuth({ provider, options: { redirectTo: `http://example.com/auth/callback`, },})

At the callback endpoint, handle the code exchange to save the user session.

Create a new file at app/auth/callback/route.ts and populate with the following:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
import { NextResponse } from 'next/server'// The client you created from the Server-Side Auth instructionsimport { createClient } from '@/utils/supabase/server'export async function GET(request: Request) { const { searchParams, origin } = new URL(request.url) const code = searchParams.get('code') // if "next" is in param, use it as the redirect URL const next = searchParams.get('next') ?? '/' if (code) { const supabase = await createClient() const { error } = await supabase.auth.exchangeCodeForSession(code) if (!error) { const forwardedHost = request.headers.get('x-forwarded-host') // original origin before load balancer const isLocalEnv = process.env.NODE_ENV === 'development' if (isLocalEnv) { // we can be sure that there is no load balancer in between, so no need to watch for X-Forwarded-Host return NextResponse.redirect(`${origin}${next}`) } else if (forwardedHost) { return NextResponse.redirect(`https://${forwardedHost}${next}`) } else { return NextResponse.redirect(`${origin}${next}`) } } } // return the user to an error page with instructions return NextResponse.redirect(`${origin}/auth/auth-code-error`)}

If your user is already signed in, Discord prompts the user again for authorization.

When your user signs out, call signOut() to remove them from the browser session and any objects from localStorage:

1
2
3
async function signOut() { const { error } = await supabase.auth.signOut()}

Resources