AI & Agent Dev Bug Sandbox Back to Radar

Linkedin_oidc Provider Uses Api.Linkedin.Com For The Authorization Redirect Instead Of Www.Linkedin.Com

The LinkedIn OIDC provider builds its OAuth authorization and token URLs against api.linkedin.com instead of LinkedIn's documented www.linkedin.com endpoint, causing users with an active linkedin.com session to be forced to log in again on every sign-in attempt.

highConfidence 90%Supabase

Origin Analysis

In internal/api/provider/linkedin_oidc.go, the constant defaultLinkedinOIDCAPIBase is set to "api.linkedin.com". This host is LinkedIn's REST API host, not the interactive OAuth authorization host, and it does not share session cookies with www.linkedin.com. Consequently, when the provider constructs AuthURL and TokenURL using this base, the authorization request redirects to a domain that cannot recognize the user's existing LinkedIn session, forcing a full login.

1. Enable LinkedIn (OIDC) provider in a Supabase project with valid LinkedIn app credentials. 2. From a browser that already has an active linkedin.com session, call supabase.auth.signInWithOAuth({ provider: "linkedin_oidc" }). 3. Observe the network redirect chain: it goes to api.linkedin.com/oauth/v2/authorization, then to www.linkedin.com/uas/login?session_redirect=... with a full username/password prompt. 4. Compare with a direct authorization request to www.linkedin.com/oauth/v2/authorization, which shows the expected "Continue as [Name]" consent screen.

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

Self-hosted deployments that provide a custom external URL via extension will not be affected. After deploying this change, verify that token exchange succeeds against www.linkedin.com/oauth/v2/accessToken. If any enterprise LinkedIn application still relies on api.linkedin.com for the token endpoint, roll back only the TokenURL change while keeping AuthURL on www.linkedin.com. Test in a staging environment before production rollout. To roll back, revert the two constant values to api.linkedin.com.