new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Supabase · Auth · all subjects

oauth providers/linkedin

11 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

LinkedIn OAuth setup overview

Setting up LinkedIn logins consists of three parts: Create and configure a LinkedIn Project and App on the LinkedIn Developer Dashboard, add the LinkedIn (OIDC) client_id and client_secret to the Supabase Dashboard, and add login code to the Supabase JS Client App.

LinkedIn OIDC provider name in signInWithOAuth

When calling signInWithOAuth() to enable LinkedIn login, use 'linkedin_oidc' as the provider parameter.

LinkedIn OAuth app creation steps

To create a LinkedIn OAuth app: Go to LinkedIn Developer Dashboard and log in, click Create App at the top right, enter your LinkedIn Page and App Logo, save your app, click Products from the top menu, look for Sign In with LinkedIn using OpenID Connect and click Request Access, click Auth from the top menu, add your Redirect URL to the Authorized Redirect URLs section, and copy and save the generated Client ID and Client Secret. Ensure appropriate scopes have been added under OAuth 2.0 Scopes at the bottom of the Auth screen.

Management API configuration for LinkedIn OIDC

LinkedIn (OIDC) auth provider can be configured using the Management API with a PATCH request to https://api.supabase.com/v1/projects/{PROJECT_REF}/config/auth with the following JSON body: external_linkedin_oidc_enabled (boolean), external_linkedin_oidc_client_id (string), external_linkedin_oidc_secret (string). Authentication requires a Bearer token from https://supabase.com/dashboard/account/tokens.

LinkedIn OIDC provider replaces legacy LinkedIn provider

Supabase is replacing the legacy LinkedIn provider with a new LinkedIn (OIDC) provider to support recent changes to LinkedIn OAuth APIs and the Open ID Connect standard. The legacy LinkedIn provider edits were disabled and it will be removed effective 4th January 2024. Developers with LinkedIn OAuth Applications created prior to 1st August 2023 should create a new OAuth application or add the Sign In with LinkedIn using OpenID Connect product to their existing application.

Supabase CLI config for LinkedIn OIDC

In config.toml for Supabase CLI, configure LinkedIn OIDC auth provider using: [auth.external.linkedin_oidc] with fields enabled (boolean), client_id (string), and secret (string).

JavaScript signInWithOAuth example for LinkedIn

import { createClient } from '@supabase/supabase-js' const supabase = createClient('https://your-project-id.supabase.co', 'sb_publishable_...') async function signInWithLinkedIn() { const { data, error } = await supabase.auth.signInWithOAuth({ provider: 'linkedin_oidc', }) }

Flutter signInWithOAuth example for LinkedIn

Future<void> signInWithLinkedIn() async { await supabase.auth.signInWithOAuth( OAuthProvider.linkedinOidc, redirectTo: kIsWeb ? null : 'my.scheme://my-host', authScreenLaunchMode: kIsWeb ? LaunchMode.platformDefault : LaunchMode.externalApplication, ); }

Kotlin signInWith example for LinkedIn

suspend fun signInWithKaLinkedIn() { supabase.auth.signInWith(LinkedIn) }

C# SignIn example for LinkedIn OIDC

var state = await supabase.Auth.SignIn(Provider.LinkedInOIDC); var signInUrl = state.Uri;

LinkedIn OAuth uses PKCE flow

LinkedIn OAuth sign-in with Supabase implements the PKCE (Proof Key for Code Exchange) flow for enhanced security.

Give your agent this brain