Announcement Announcement Module
No announcement yet.
LinkedInConnectionFactory for OAuth2 Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • LinkedInConnectionFactory for OAuth2

    Spring Social source contains an implementation of LinkedInConnectionFactory that extends OAuth1ConnectionFactory<LinkedIn>.

    Is there a corresponding implementation that extends OAuth2ConnectionFactory<LinkedIn>?

    I started writing my own and found myself having to write a corresponding ServiceProvider class & an Adapter class. But then to implement the getApi() method of AbstractOAuth2ServiceProvider, I will need to write a LinkedInTemplate that extends AbstractOAuth2ApiBinding.

    Am I missing something here or am I on the right track and will have to code in all the above classes to obtain OAuth2 support.

    Please advise.


  • #2
    My bad!
    Just found out that LinkedIn does not support OAuth2 yet! That explains why Spring Social does not have these classes built in. Sorry for missing that!
    Well, the main reason I wished to implement OAuth2 is to utilize the 'scope' parameter to provide member permissions. But I suppose Spring Social does not support that yet as per the below thread.


    • #3
      You're right, LinkedIn doesn't support OAuth 2...and Spring Social does not yet support custom parameters to the level needed to support scope for LinkedIn.

      But I can certainly see how that would be useful. If you've not done so already, please vote up the issue that mentions this. It's not currently on the roadmap for the next milestone of Spring Social 1.1.0, but I might consider bumping it up.


      • #4
        Could you please provide the link where I could vote up the issue?

        Last edited by praveenpillai; Dec 18th, 2012, 01:00 PM.


        • #5
          Sorry about that. I was thinking that your request pertained to, but as mentioned in the forum post that you referred to that has to do with sending additional parameters during authorization whereas what you'll need is to send additional parameters at the time you fetch the request token.

          So, I've created a new improvement issue at to track this. Vote it up!


          • #6
            Thanks Craig. Voted up!