LinkedIn OAuth unauthorized_scope_error: switch to the OIDC provider

TL;DR

Fix: switch your Supabase project's LinkedIn provider configuration to the new LinkedIn OIDC provider, which is in production. The OIDC provider replaces the deprecated method and the error goes away.

Steps

1. Sign in with LinkedIn failing with unauthorizedscopeerror: LinkedIn deprecated the old OAuth method. Fix: switch your Supabase project's LinkedIn provider configuration to the new LinkedIn OIDC provider, which is in production. The OIDC provider replaces the deprecated method and the error goes away. Maintainer-confirmed.

When to use

You are seeing this: Supabase Auth - 'unauthorizedscopeerror' for LinkedIn. Use this skill when you run into "LinkedIn OAuth unauthorizedscopeerror: switch to the OIDC provider".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/supabase/auth/issues/1216

In gh:supabase/auth#1216 (https://github.com/supabase/auth/issues/1216), the issue reported: 'unauthorizedscopeerror' for LinkedIn. Current LinkedIn OAuth method is deprecated: signing in with LinkedIn fails with unauthorizedscopeerror. The verified answer: Sign in with LinkedIn failing with unauthorizedscopeerror: LinkedIn deprecated the old OAuth method. Fix: switch your Supabase project's LinkedIn provider configuration to the new LinkedIn OIDC provider, which is in production. The OIDC provider replaces the deprecated method and the error goes away. Maintainer-confirmed.