Uploaded image for project: 'Confluence Server'
  1. Confluence Server
  2. CONFSERVER-45201

Invalid AppID is generated when upgrading from 5.10.x to 6.0.x

    Details

    • Symptom Severity:
      Major
    • Support reference count:
      8
    • Sprint:
      Enterprise is lovely
    • Testing Notes:
      Hide
      • Install Confluence 5.10.6 with a license that contains non-romantic organisation name.
      • Upgrade it to Confluence 6.0.1 (i.e. run Confluence 6.0, which will use the same home directory of the 5.10.6 instance). After being upgraded, test if collabortive editing works (it is expected to fail).
      • Deploy a new version of collaborative editor plugin to your Confluence 6.0 instance. Collaborative editing should work now.
      Show
      Install Confluence 5.10.6 with a license that contains non-romantic organisation name. Upgrade it to Confluence 6.0.1 (i.e. run Confluence 6.0, which will use the same home directory of the 5.10.6 instance). After being upgraded, test if collabortive editing works (it is expected to fail). Deploy a new version of collaborative editor plugin to your Confluence 6.0 instance. Collaborative editing should work now.
    • Occurrence Factor:
      25%
    • Development Effort:
      M

      Description

      When upgrading from 5.10.x to 6.0.1 and Confluence is not able to connect to Synchrony.

      Root Cause Analysis

      The AppID that contains the non-romantic Unicode organisation name has been stored in the Confluence 5.10.x's database. When Confluence is upgraded to 6.0.1, theĀ AppID is not re-generated but retrieved from the corresponding table and Synchrony is not able to talk to Confluence with that old AppID.

      Workaround

      This issue can be fixed by turning Collaborative editing mode off and on as in the following screenshot:

      1. Click the Change Mode button, select OFF in the dialog, and click Change.
      2. Turn it ON again with the same steps above.
      If you have a Confluence page open, please make sure to refresh the page before clicking the Edit button.
      Please note that restarting Synchrony (by clicking the Restart Synchrony button) will not resolve this issue.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Last commented:
                  42 weeks, 3 days ago