apps/docs/content/guides/auth/social-login/auth-linkedin.mdx
To enable LinkedIn Auth for your project, you need to set up a LinkedIn OAuth application and add the application credentials to your Supabase Dashboard.
Setting up LinkedIn logins for your application consists of 3 parts:
client_id and client_secret to your Supabase Project.<$Partial path="social_provider_setup.mdx" variables={{ "provider": "LinkedIn" }} />
Create App at the top rightLinkedIn Page and App LogoProducts from the top menuSign In with LinkedIn using OpenID Connect and click on Request AccessAuth from the top menuRedirect URL to the Authorized Redirect URLs for your app sectionClient IDClient SecretEnsure that the appropriate scopes have been added under OAuth 2.0 Scopes at the bottom of the Auth screen.
<$Partial path="social_provider_settings_supabase.mdx" variables={{ "provider": "LinkedIn (OIDC)" }} />
You can also configure the LinkedIn (OIDC) auth provider using the Management API:
# Get your access token from https://supabase.com/dashboard/account/tokens
export SUPABASE_ACCESS_TOKEN="your-access-token"
export PROJECT_REF="your-project-ref"
# Configure LinkedIn (OIDC) auth provider
curl -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_linkedin_oidc_enabled": true,
"external_linkedin_oidc_client_id": "your-linkedin-client-id",
"external_linkedin_oidc_secret": "your-linkedin-client-secret"
}'
<Tabs scrollable size="small" type="underlined" defaultActiveId="js" queryGroup="language"
<TabPanel id="js" label="JavaScript">
<$Partial path="create_client_snippet.mdx" />
When your user signs in, call signInWithOAuth() with linkedin_oidc as the provider:
import { createClient } from '@supabase/supabase-js'
const supabase = createClient('<your-project-url>', '<sb_publishable_... or anon key>')
// ---cut---
async function signInWithLinkedIn() {
const { data, error } = await supabase.auth.signInWithOAuth({
provider: 'linkedin_oidc',
})
}
When your user signs in, call signInWithOAuth() with linkedin_oidc as the provider:
Future<void> signInWithLinkedIn() async {
await supabase.auth.signInWithOAuth(
OAuthProvider.linkedinOidc,
redirectTo: kIsWeb ? null : 'my.scheme://my-host', // Optionally set the redirect link to bring back the user via deeplink.
authScreenLaunchMode:
kIsWeb ? LaunchMode.platformDefault : LaunchMode.externalApplication, // Launch the auth screen in a new webview on mobile.
);
}
When your user signs in, call signInWith(Provider) with LinkedIn as the Provider:
suspend fun signInWithKaLinkedIn() {
supabase.auth.signInWith(LinkedIn)
}
<$Partial path="oauth_pkce_flow.mdx" />
<Tabs scrollable size="small" type="underlined" defaultActiveId="js" queryGroup="language"
<TabPanel id="js" label="JavaScript">
When your user signs out, call signOut() to remove them from the browser session and any objects from localStorage:
import { 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()
}
When your user signs out, call signOut() to remove them from the browser session and any objects from localStorage:
Future<void> signOut() async {
await supabase.auth.signOut();
}
When your user signs out, call signOut() to remove them from the browser session and any objects from localStorage:
suspend fun signOut() {
supabase.auth.signOut()
}
We will be replacing the LinkedIn provider with a new LinkedIn (OIDC) provider to support recent changes to the LinkedIn OAuth APIs. The new provider utilizes the Open ID Connect standard. In view of this change, we have disabled edits on the LinkedIn provider and will be removing it effective 4th January 2024. Developers with LinkedIn OAuth Applications created prior to 1st August 2023 should create a new OAuth application via the steps outlined above and migrate their credentials from the LinkedIn provider to the LinkedIn (OIDC) provider. Alternatively, you can also head to the Products section and add the newly releaseSign In with LinkedIn using OpenID Connect to your existing OAuth application.
Developers using the Supabase CLI to test their LinkedIn OAuth application should also update their config.toml to make use of the new provider:
[auth.external.linkedin_oidc]
enabled = true
client_id = ...
secret = ...
Do reach out to support if you have any concerns around this change.