Topic-icon LinkedIn changed API, now requires "scope" variable for many fields

Active Subscriptions:

None
Was struggling with JLinked first because LinkedIn api wants the fully-qualified domain name, which I didn't have because I was on a virtual machine. Moved to a live machine with fully-qualified domain name and authentication worked but not all data was being imported. Just requested a refund because I thought this plugin was broken... then had second thoughts and did some digging.

LinkedIn developer site identified some of these problem fields as requiring "r_fullprofile" member permission. Found my way to the php wrapper you are using and found that this is a open issue on their bug list (added two days ago). In file named linkedin_3.1.1.php line 179, I changed to
const _URL_REQUEST = 'https://api.linkedin.com/uas/oauth/requestToken?scope=r_fullprofile';

Now when I sign in for the first time, I get the message that my website is requesting Full Profile Access, instead of Basic Profile Access. Still working on it, but it looks like LinkedIn may have changed some of the field names also.

If anyone else has some ideas, please reply. I am more lucky than I am knowledgeable.
The topic has been locked.
Active Subscriptions:

None
Contacted the developer who created the php LinkedIn API wrapper. He acknowledged LinkedIn made changes earlier in the week, but did not have an ETA on when he could dedicate time to update the wrapper. As he is an unpaid developer donating his time, SourceCoast may need to look at an alternate library if it's to be resolved in the short term.

My previous post about the hard coded "scope" addition may be enough for short term.
The topic has been locked.
Support Specialist
Yeah, we're working on dealing with some of the changes ourself and actually had been planning a new low-level file of our own, instead of the library we're using.

The good news is that the new scope parameter actually allows for email address to be imported (from the quick investigation we've done). If so, that will be a huge benefit for other features we can implement.

We'll have a new release out hopefully later this week with some compatibility updates, but not necessarily new features.

Sorry for the inconvenience, and thanks for the report! Definitely let us know if you run into any other issues, and we'll keep you posted on what we find.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
Using the workaround we posted up top, we were able to import all the JLinked available fields with the exception of skills, urls, address, phone numbers, twitter account, and date of birth. Maybe we are using the wrong field types?

This is what we have tried;
Twitter Account - Textarea/ text field
URLs - Textarea/ text field / webaddress
Skills - Textarea/ text field
Address - Textarea/ text field
Phone numbers - Textarea/ text field
DOB - Textarea/ textf ield/ date (we get the attached error for date field)
File Attachment:
The topic has been locked.
Support Specialist
You'll want to update the line to look like:
const _URL_REQUEST = 'https://api.linkedin.com/uas/oauth/requestToken?scope=r_fullprofile+r_contactinfo';
The contactinfo is for "Address, phone number, and bound accounts", which sounds like other things you want.

For all the new scope permissions, see:
developer.linkedin.com/documents/authentication#granting

Going along with that, I'd highly recommend just going ahead and adding +r_emailaddress to the URL above. With JFBConnect, the email is an optional permission (for Facebook), but we always require it anyways. Since Joomla always needs an email address, it just makes it easier to require it of everyone. When we release our update, we'll most likely make that a required permission as well. Then, we'll also be able to add the auto-account creation functionality to JLinked as well, which makes registration a one-click process.

Hope that helps, and let us know what you find!
Alex
The topic has been locked.
Active Subscriptions:

None
Made the change. Seems to work the same.
Any ideas on the fields question I had?

Thanks.Greg
The topic has been locked.
Support Specialist
Address and phone number should work with the r_contactinfo. Twitter, skills, and URLs should be in the r_fullprofile.

When you made that change and tried to re-authenticate with LinkedIn again, was there a new permissions window? It should ask for more permissions. However, the documentation on this new feature is severly lacking. As you can see in the link I posted above, there's different options like "All or none" and "Re-Auth on Permission changes". However, there isn't information on how to set those options.

As for the birthday field, we'll have to look into that more. That sounds like an issue on our end where we're not parsing out the date they send back properly. What profile plugin are you using? We'll have to test with that one to understand where the problem lies. I'd recommend disabling the birthday field for now while you work through the other issues.

Finally, please note that profile import only occurs in JLinked on new user account registration. If you are simply re-logging in, the new fields won't be imported. Another thing to try is to delete your application from your LinkedIn User's profile. That way, when you re-authenticate, your assured you'll get the permission popup properly. You can delete the app from your profile by going to www.linkedin.com/settings/ and clicking on "Groups, Companies and Applications" and then "View Applications".

Keep us posted,
Alex
The topic has been locked.
Active Subscriptions:

None
Yes. Re-authentication shows new permissions. Also, cleared out the application permissions as you suggested.

File Attachment:


Because this is a dev site, I have all the fields show up during registration. That way when I LinkedIn register, it prefills all the fields for a quick look at what fails to come in. If I don't click register, then I can fiddle around with the fields again, and see what is broken without having to remove the user.

Other than the fields I mentioned, it seems to be working.
I'll send you admin details so you can mess with it a bit. (dev Site... can't hurt it)

Thanks, Greg
The topic has been locked.
Active Subscriptions:

None
Send me a message so I can send the credentials.
The topic has been locked.
Support Specialist
You can Private Message me by clicking the arrow under my picture (<
) and hitting the mail icon.

Please let me know exactly what you'd like me to look at. I'll definitely check out the birthday issue, but beyond that, if there are other specific fields you're having issues with, let me know. It seems like some of the ones in the list you mention above may be better now, but just not sure.

Thanks,
Alex
The topic has been locked.