Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 25.0.0
    • Fix Version/s: 25.0.0
    • Component/s: None
    • Labels:
    • Story Points:
      3
    • Sprint:
      2019.9 - IDM

      Description

      As found by OPENIDM-12696, Linkedin no longer works as part of our generic OAuth2Client implementation.

      Upon investigation, it has been discovered this failure is due to our addition of PKCE suppport. Linkedin fails on the accessToken endpoint when any additional parameters with an "Access Denied". Linkedin doesnt support PKCE unless it is for a native application https://docs.microsoft.com/en-us/linkedin/shared/authentication/authorization-code-flow-native?context=linkedin/sales/context 

      Additionally, as of May 1 2019, Linkedin no longer supports its v1 APIs. Their v2 API now separates the retrieval of profile information and email address into two separate APIs. Due to this we now need a custom linkedin client to accommodate their new APIs.
      https://docs.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/migration-faq?context=linkedin/consumer/context

      Acceptance Criteria:

      A new linkedin client to support the v2 API

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                krismy.alfaro Krismy Alfaro
                Reporter:
                krismy.alfaro Krismy Alfaro
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: