LinkedIn connection deprecated?

[phill_truebase]

Hi Konrad, Thanks for the updates throughout the thread.

Given that we’re now just two weeks away from the deadline to make the update, is there any news to share?

Also, while reviewing the Sign In with LinkedIn documentation, it appears that they include support for an additional permission r_emailaddress which provides the member’s email address.

Does this mean that we’ll continue to receive the user’s email address after the transition?

Thanks,
Phill

[adrogon]

@phill_truebase

Also, while reviewing the Sign In with LinkedIn documentation, it appears that they include support for an additional permission r_emailaddress which provides the member’s email address.

Does this mean that we’ll continue to receive the user’s email address after the transition?

r_emailaddress already exists in v1.
It is added to the list of scopes when you check “Connections > Social > LinkedIn > Settings > Attributes > Email address” in your Auth0 tenant.

I second your concern though. If v1 really dies in 2 weeks, and there is anything for us to do to upgrade to v2, now would be the right time to communicate about the changes.
Even if they are not ready to be implemented, but at least to know what to expect, thank you.

[James.Morrison]

Heads up on some recent news in our Announcements section concerning important changes to the LinkedIn Connections!

Important changes in LinkedIn Connections

On December 2018, LinkedIn deprecated the current version of their sign-in API, announcing the final shutdown for March 1st 2019. In its place, LinkedIn has provided a new version of the sign-in API with some differences. It is possible that you will need to adjust your application code when using the new API. We added a way to let you select which LinkedIn API version you want to use. To do that, you can update the ‘Strategy Version’ for your Linkedin Connection in the Auth0 Dashboard. In Mar…

[phill_truebase]

Thanks for cross posting the announcement to this thread.

[adrogon]

Looks ok for us so far without modifying our code. We’ll keep you updated if something comes up.
In the meantime, thank you for the resolution

[konrad.sopala]

Sure! Let us know in this thread if you have any questions related to that in the future!

[Nico-92]

@konrad.sopala When using the v1 on Auth0, requesting only the profile (not the full profile) attribute, a field called publicProfileUrl was returned as part of the Auth0’s user object.
I switched Auth0 to v2 and select both the profile and basic profile checkbox, but the publicProfileUrl is not part of the user anymore.
How can we get that back? It’s essential for the login flow that we use.

According to the basic profile specs the vanityName should be part of the returned fields. The vanityName is important because it is used for the public profile URL. vanityName is also missing from the Auth0’s user object.

[andres.aguiar]

Hi @Nico-92

Did you get enrolled in one of Linkedin Developer Enterprise products?

You need that if you want to get the Basic Profile

Self-Serve Migration FAQ - LinkedIn