Azure AD B2C LinkedIn IDP does not work

Question

Using the standard options to add LinkedIn as an identity provider on my B2C tenant does not work.

Seems like the current integration is still using r_emailaddress and r_liteprofile scopes, which are not support by the new LinkedIn OpenID specification.

Answer 1

Hi @Anderson Rancan ,

Thanks for reaching out.

LinkedIn recently made changes to their approved scope which was initially r_emailaddress and r_liteprofile due to which getting below error:

AAD2C90273: An invalid response was received: Error: unauthorized_scope_error, Error Description: Scope "r_emailaddress" is not authorized for your application.

We have identified the new scope would be openid profile email in Linkedin.

Our product team is working on it and will update the changes soon in the documentation.

Thanks for your time and patience throughout this scenario.

Thanks,

Shweta

Answer 2

Thank you @Shweta Mathur for your reply.

In that case I'll wait for news about the topic.

I'd like to select your comment as the accepted answer, but I don't see the option.

Answer 3

Hello,

I am still facing the same issue.
I also checked the documentation:
https://learn.microsoft.com/en-us/azure/active-directory-b2c/identity-provider-linkedin?pivots=b2c-user-flow
and have followed all the steps.

Is there any estimation when this is going to be fixed?

Thank,
George

Answer 4

Hi

Same here. 5 months to update scope names? Come on

Answer 5

Hello. The same here. Any news on this, please? I do not want to complicate any further with custom policies (tried this for LinkedIn, and lost the whole day without succeeding). Pls if that can be resolved, if possible (it is under the same roof, damn :)). For my business-type app targeted at professionals, it comes across much better to have LinkedIn as a social IDP, than say Facebook or similar. So, it is important for that type of use cases, I guess ... Cheers