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?
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.
@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.