Linkedin integration issue using socialauth in android

I included bindinintartion in my android app using socialauth a year ago. It worked fine until a few days ago. Now it gives the following error:

"org.brickred.socialauth.exception.SocialAuthConfigurationException: Application keys are invalid. The server that the application is running on must be the same as for registering keys."

Tried using the following default keys.

api.linkedin.com.consumer_key = bh82t52rdos6
api.linkedin.com.consumer_secret = zQ1LLrGbhDZ36fH8

      

Getting the same error for the app keys generated earlier, the default app keys and for the newly created app.

Any idea why this is happening? Are there any changes to related APIs?

Libds included : socialauth-4.4.jar, socialauth-android-3.2.jar.

+3


source to share


4 answers


This is due to a change in the Linked in Developer program. The changes are mentioned here https://developer.linkedin.com/support/developer-program-transition .

You are getting this error because the default scope setting in r_fullprofile

, which is part of the change, is no longer available.



So, to apply these changes to the socialauth API, you must pass the scope permission as <prop key="api.linkedin.com.custom_permissions">r_basicprofile,r_emailaddress</prop>

+1


source


Linkedin updated their Scope for API, they updated their API link: https://developer.linkedin.com/support/developer-program-transition

The following are profile fields for all LinkedIn developers: Primary profile fields Location fields Location fields

These fields are not



Full Profiles Contact Information Company Fields Publication Fields Patent Fields Language Fields Skill Fields Certification Fields Course Fields Education Fields Volunteer Fields Reference Fields.

Additionally, only these profile APIs // v 1 / people / ~ Share API - / v1 / people / ~ / shares Companies API - / v1 / companies / {id} will work.

Check the scope.

0


source


LinkedIn blocked many parts of their APIs on May 12, 2015 according to https://developer.linkedin.com/blog/posts/2015/developer-program-changes

Since you are using the socialauth library, you will have to wait for its developers to use the new version. :(

0


source


Downloading library 4.9 solves this problem You can get the jar directly from Maven: http://search.maven.org/remotecontent?filepath=org/brickred/socialauth/4.9/socialauth-4.9.jar

0


source







All Articles