---
title: "LinkedIn Migrating to OpenID Connect"
url: https://docs.catalyst.zoho.com/en/announcements/2024/linkedin-announcement/
last_updated: 2026-04-07T14:25:28Z
service: All Services
type: general
related_links:
  - name: "Configuring LinkedIn Identity Provider"
    url: /en/cloud-scale/help/authentication/social-logins/configuring-social-logins/#enable-linkedin-social-login/
---

# LinkedIn Migration to OpenID Connect from OAuth

LinkedIn has [announced](https://www.linkedin.com/developers/news/featured-updates/openid-connect-authentication) their decision to migrate from `OAuth` protocols to `OpenID Connect` protocols on **January 10, 2023**. As per their announcement, they have implemented this change to provide an additional identity layer of security over the `OAuth` protocols. This change will affect our users who have implemented the LinkedIn Identity Provider's Authentication for their Catalyst application.

The new scopes that you will be configuring in the [LinkedIn developer portal](https://www.linkedin.com/developers/) are listed below.

<table class="content-table">
	<thead>
		<tr>
			<th class="w25p">Scope</th>
			<th class="w75p">Purpose</th>
		</tr>
	</thead>
	<tbody>
		<tr>
			<td>`openid`</td>
			<td>To indicate the application wants to use OIDC to authenticate the member.</td>
		</tr>
        <tr>
			<td>`profile`</td>
			<td>To get the member's lite profile including their id, name, and profile picture.</td>
		</tr>
        <tr>
			<td>`email`</td>
			<td>To get the member's email address</td>
		</tr>
	</tbody>
</table>

For more information on `OpenID Connect` protocols, visit their [official documentation](https://learn.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/sign-in-with-linkedin-v2).

In light of this new change, we urge you to regenerate your authentication tokens using `OpenID Connect` protocols. The steps to generate `ClientID` and `Client Secret` tokens can be found our [help documentation](https://docs.catalyst.zoho.com/en/cloud-scale/help/authentication/social-logins/configuring-social-logins/#enable-linkedin-social-login). 

LinkedIn has additionally stated that if their end-users have implemented LinkedIn identity providers for their applications before **August 2023**, they will continue to support `OAuth` and `OpenID Connect` protocols for them for an unspecified extended time period. However, given the ambiguity on it's deprecation date, we urge you to to migrate your projects that use LinkedIn signups from `OAuth` protocols to `OpenID Connect` protocols as soon as possible.

LinkedIn has additionally stated that if their end-users have implemented LinkedIn identity providers for their applications before **August 2023**, they will continue to support `OAuth` and `OpenID Connect` protocols for them for an unspecified extended time period. However, given the ambiguity on it's deprecation date, we urge you to to migrate your projects that use LinkedIn signups from `OAuth` protocols to `OpenID Connect` protocols as soon as possible.
Scope	Purpose
`openid`	To indicate the application wants to use OIDC to authenticate the member.
`profile`	To get the member's lite profile including their id, name, and profile picture.
`email`	To get the member's email address