LinkedIn OAuth login adds Sign in with Google and Sign in with Apple from December 2, 2025
What changed
LinkedIn's November 2025 release notes (version 202511) say that from December 2, 2025, the LinkedIn login page shown during OAuth authorization offers Sign in with Google and Sign in with Apple in addition to username and password. Apps that follow the standard OAuth specification should need no change. The authorization code flow docs now also list passkey login, say these options work on desktop and Android web browsers only, and describe an enable_extended_login=true parameter for other platforms. Apps can opt out through a Developer Support request.
What it means
Members connecting a LinkedIn account to an app through OAuth can log in to LinkedIn with Google or Apple, alongside username and password, on desktop and Android web browsers.
Who is affected
Every scheduler, analytics and publishing tool that connects LinkedIn accounts through the OAuth 2.0 authorization code flow, especially ones that open the login page in an embedded web view or a native app.
What to do by 2 Dec 2025
Test your LinkedIn connect flow with the Google and Apple options. Follow the standard OAuth pattern for native apps (RFC 8252), and use enable_extended_login=true if you need the options outside desktop and Android browsers.
What this means for you
When you connect LinkedIn to a posting app, LinkedIn asks you to log in first. Since December 2, 2025, that login page also lets you use your Google or Apple account, if that is how you sign in to LinkedIn. Your old password login still works. If they don't work inside an app, the app may need a fix.
The details
- Date: December 2, 2025, announced in the November 2025 release (version
202511). - Where: the LinkedIn login step of
/oauth/v2/authorizationin the 3-legged authorization code flow. All authentication stays on LinkedIn's domain. - Platforms: LinkedIn says Google and Apple login (and passkey login, which the current docs also list) work on desktop and Android web browsers only. To offer them elsewhere, such as in native apps, add
enable_extended_login=trueto the authorization request. - Compatibility: apps that start OAuth the standard way for native apps (RFC 8252, which means a system browser rather than an embedded web view) should work without changes. LinkedIn's docs point to the flow guide for testing the new options.
- Unchanged: username and password login keeps working.
- Opting out: send a Developer Support request if you want the extra login options turned off for your app.
What to do next
- Business owners: Nothing. You can now use Google or Apple to log in when you connect LinkedIn to a tool.
- Marketers and agencies: Nothing, but if a client can't connect LinkedIn through Google or Apple login, ask the tool's support about it.
- Developers: Run your LinkedIn connect flow with Google and Apple login on each platform you support, and move any embedded web view login to a system browser.
Primary sources
- LinkedIn Marketing API: Recent Marketing API Changes (November 2025)
- LinkedIn: Authorization Code Flow (3-legged OAuth), Step 2
Get an email when a new API change is added
Follow new entries with the RSS feed. Each platform also has its own feed, for example X or Meta.