Sending incorrect oauthClientId to installation callback on site rename for Connect on Forge apps

XMLWordPrintable

    • Minor
    • Unit testing
    • S

      When a site is renamed, this triggers the apps' installation lifecycle hook so that they can receive the new base url. 

      For Connect on Forge apps, the installation hook will incorrectly receive the Forge oauthClientId as opposed to the Connect oauthClientId, causing subsequent user impersonation requests in the Connect remote to fail.

            Assignee:
            Serena Wang
            Reporter:
            Serena Wang
            Votes:
            70 Vote for this issue
            Watchers:
            36 Start watching this issue

              Created:
              Updated:
              Resolved: