Postponed (maintainer needs more info)
Project:
LinkedIn Integration
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 Jan 2011 at 17:40 UTC
Updated:
5 Feb 2016 at 14:42 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
davad commentedThe debug message needs to be fixed. It's currently not outputting anything useful, as you found. Double check that your API key and secret key are setup correctly.
Comment #2
sol roth commentedMy API key and secret are correct and I have this same issue, Using Oauth 6.3X. I'm using the latest stable version (will test with dev after this).
Comment #3
sol roth commentedWhn I authorize the app it only asks for "You Profile Overview" Permission, it's missing the allow access to "network updates", this is probably why posting content is not working.
Comment #4
sol roth commentedSee this example
http://developer.linkedin.com/documents/authentication#granting
Specifically:
http://api.linkedin.com/uas/oauth/requestToken?scope=r_basicprofile+r_em...
I went through the module, but I'm not sure where to add the authentication (scope) parameter to make sure the application has read / write permissions. Can the module maintainer give me a heads up or an idea on how to fix? The login and everything seems to work great for the actions that work with the default profile permission.
Comment #5
sol roth commentedOk, after some looking, I have a working temporary fix until the permissions properly propagate from the submodules (like linkedin_status).
For Linkedin Integration 6.x-1.dev, open up linkedin.inc.
Find
$url = $base_url . "/requestToken";Replace with
$url = $base_url . "/requestToken?scope=rw_nus";Replace rw_nus with any of the additional permissions you want to grant the application according to the current LinkedIn API. rw_nus allows networking updates (status) and will allow the linkedin_status module to function properly. I didn't make a patch, because it's not a "proper" fix, but it works :).
Comment #6
davad commentedAt #5, I'm not sure what the "proper" fix would be then. The 7.x branch needs that too.
Comment #7
sol roth commentedThe approach is correct approach as far as the URL for authorizing permissions, but putting it in the base url will "hard" code it into asking the same permissions no matter what sub-modules you are using. For example if you're not going to use the Linkedin status module you may not need the RW permission. There should be a way to hook into it and add on extra permissions as needed.
Comment #8
bobleanca@gmail.com commentedHi,
I have the same problem. I changed url assign line with $url = $base_url . "/requestToken?scope=rw_nus"; cleared all caches, and still can't post:
And nothing appears in linkedin.
All tests with admin user, and Linkedin account correctly set to the admin.
Maybe i missed something in the configuration of the application? Could anybody tell me what is Integration URL?
In API Usage Report in LinkedIn i got:
Get My Profile Call Count: 1 Allowed: 100000
Post Share Call Count: 1 Allowed: 125000 ?!?!
I would really appreciate if anybody could help!
OAuth version: 7.x-3.1
LinkedIn Integration: 7.x-1.x-dev
Comment #9
thetech249 commentedMake sure you have gone to your linkedin app and enabled rw_nus under default scope.
Comment #10
Joel_Geurts commentedHey, Just in case it's useful to someone here is the fix I settled on.
This fix was performed on the 7.x release.
Go to your linkedin.inc file in the module's directory and locate the line that sets $url variable like:
$url = $base_url . "/requestToken";I added this line of code above it:
$scope = (module_exists('linkedin_status') && !$anon) ? "?scope=rw_nus":"";Then I simply added that variable to the end of $url like:
$url = $base_url . "/requestToken" . $scope;This fix will check if user is logged in already and if the linkedin status sub-module is enabled, and only add the scope property if both are true.