Uploaded image for project: 'Keycloak'
  1. Keycloak
  2. KEYCLOAK-9185

Update LinkedIn social login provider to use new v2 user profile APIs before 1st March 2019

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 3.4.3.Final
    • Fix Version/s: 4.8.3.Final
    • Component/s: None
    • Labels:
      None

      Description

      I received next email from LinkedIn (some unimportant parts removed), which states that some login related APIs stop to work on 1st March 2019:

      Hello Vlastimil,

      The LinkedIn Developers program helps app creators and website owners provide personalized experiences to our members, gives members the ability to use their professional identity with other services, and makes it easier to share content from other sites on LinkedIn. Today, we're announcing several updates that will migrate all of our developers to the latest set of technologies used for our third-party integrations. We are also streamlining our programs, so we can provide better support to the entire LinkedIn developer community. Providing members with clarity and control over the use of their data is a fundamental priority for LinkedIn, and these changes also serve to advance this priority.

      In addition to the changes listed below, all developers need to migrate to Version 2.0 of our APIs and OAuth 2.0 by March 1.

      Changes to the program include:

      ...

      To reiterate: all developers need to migrate their apps to our newest APIs and OAuth 2.0 by March 1, 2019. To help navigate the migration process, please see the technical migration guide on the LinkedIn section of the Microsoft Docs website. Developers can expect follow-up communications via email about these changes and other future announcements about the LinkedIn Developers program.

      LinkedIn provider in Keycloak had been partially updated in KEYCLOAK-6849 to use OAuth 2 API for auth and token exchange, but looks like it still uses V1 of the user profile API and older scopes, so this part have to be updated also to use new V2 API and new scopes (see https://docs.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/sign-in-with-linkedin?context=linkedin/consumer/context?trk=eml_mktg_gco_dev_api_comms)

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  pcraveiro Pedro Igor Silva
                  Reporter:
                  velias Vlastimil Eliáš
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: