Login with Slack
To enable Slack Auth for your project, you need to set up a Slack OAuth application and add the application credentials to your Supabase Dashboard.
Overview
We will be replacing the existing Slack provider with a new Slack (OIDC) provider. Developers with Slack OAuth Applications created prior to 24th June 2024 should create a new application and migrate their credentials from the Slack provider to the Slack (OIDC) provider. Existing OAuth Applications built with the old Slack provider will continue to work up till 10th October. You can refer to the list of supported scopes for the new Slack (OIDC) User.
Setting up Slack logins for your application consists of 3 parts:
- Create and configure a Slack Project and App on the Slack Developer Dashboard.
 - Add your Slack 
API KeyandAPI Secret Keyto your Supabase Project. - Add the login code to your Supabase JS Client App.
 
Access your Slack Developer account
- Go to api.slack.com.
 - Click on 
Your Appsat the top right to log in. 

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 
Authenticationicon in the left sidebar - Click on 
Providersunder the Configuration section - Click on Slack from the accordion list to expand and you'll find your Callback URL, you can click 
Copyto copy it to the clipboard 
For testing OAuth locally with the Supabase CLI see the local development docs.
Create a Slack OAuth app
- Go to api.slack.com.
 - Click on 
Create New App 
Under Create an app...:
- Click 
From scratch - Type the name of your app
 - Select your 
Slack Workspace - Click 
Create App 
Under App Credentials:
- Copy and save your newly-generated 
Client ID - Copy and save your newly-generated 
Client Secret 
Under the sidebar, select OAuth & Permissions and look for Redirect URLs:
- Click 
Add New Redirect URL - Paste your 
Callback URLthen clickAdd - Click 
Save URLs 
Under Scopes:
- Add the following scopes under the 
User Token Scopes:profile,email,openid. These scopes are the default scopes that Supabase Auth uses to request for user information. Do not add other scopes as Sign In With Slack only supportsprofile,email,openid. 
Enter your Slack credentials into your Supabase project
- Go to your Supabase Project Dashboard
 - In the left sidebar, click the 
Authenticationicon (near the top) - Click on 
Providersunder the Configuration section - Click on Slack from the accordion list to expand and turn Slack Enabled to ON
 - Enter your Slack Client ID and Slack Client Secret saved in the previous step
 - Click 
Save 
You can also configure the Slack (OIDC) auth provider using the Management API:
12345678910111213# Get your access token from https://supabase.com/dashboard/account/tokensexport SUPABASE_ACCESS_TOKEN="your-access-token"export PROJECT_REF="your-project-ref"# Configure Slack (OIDC) auth providercurl -X PATCH "https://api.supabase.com/v1/projects/$PROJECT_REF/config/auth" \  -H "Authorization: Bearer $SUPABASE_ACCESS_TOKEN" \  -H "Content-Type: application/json" \  -d '{    "external_slack_oidc_enabled": true,    "external_slack_oidc_client_id": "your-slack-client-id",    "external_slack_oidc_secret": "your-slack-client-secret"  }'Add login code to your client app
Make sure you're using the right supabase client in the following code.
If you're not using Server-Side Rendering or cookie-based Auth, you can directly use the createClient from @supabase/supabase-js. If you're using Server-Side Rendering, see the Server-Side Auth guide for instructions on creating your Supabase client.
When your user signs in, call signInWithOAuth() with slack_oidc as the provider:
123456789import { createClient } from '@supabase/supabase-js'const supabase = createClient('<your-project-url>', '<sb_publishable_... or anon key>')// ---cut---async function signInWithSlack() {  const { data, error } = await supabase.auth.signInWithOAuth({    provider: 'slack_oidc',  })}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.
1234567891011import { createClient, type Provider } from '@supabase/supabase-js';const supabase = createClient('url', 'anonKey')const provider = 'provider' as Provider// ---cut---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:
app/auth/callback/route.ts
12345678910111213141516171819202122232425262728293031323334import { 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  let next = searchParams.get('next') ?? '/'  if (!next.startsWith('/')) {    // if "next" is not a relative URL, use the default    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`)}When your user signs out, call signOut() to remove them from the browser session and any objects from localStorage:
1234567import { createClient } from '@supabase/supabase-js'const supabase = createClient('<your-project-url>', '<sb_publishable_... or anon key>')// ---cut---async function signOut() {  const { error } = await supabase.auth.signOut()}