Step 3 - Troubleshooting known issues when migrating to Security & Encryption Cloud

This page includes details of a number of known issues of secure macros that are not migrated to Cloud, together with possible solutions and workarounds.

Symptom in Confluence Cloud after migration

Cause

Solution/Workaround

Symptom in Confluence Cloud after migration

Cause

Solution/Workaround

Secure macros appear on their relevant pages as

  • Unknown macro:'secure'

or

  • Error loading the extension! 

These are Secure macros that are yet to be transformed.

  • go to the Secrets page on the left-hand side menu

  • navigate to the Server Migration tab to complete the transformation steps highlighted in the previous step

Secure macros appear in nested macros as

  • Error loading the extension!

Confluence Cloud currently does not support nested macros (See CONFCLOUD-68323) which means integration with other apps by way of nesting will be limited.

In the example below, a Secret macro is nested within an Expand macro (a standard Confluence macro).

This Secret would not be migrated unless it is moved out of the Expand macro.

 

  • as a workaround move the secrets outside of the nested macros in server before performing the migration

Failed migration

The Security & Encryption for Confluence app user must have permission at space settings for the migration to be successful. 

  • check the permission of the Security & Encryption for Confluence app user

In the example below, the app user should exist and have sufficient permissions. 

Migration is incomplete

Secure macros belonging to owners with no product access to Confluence Cloud will not be transformed correctly to Cloud - this will result in the error Migration is incomplete.

Run through the steps below

  • in server

    • find the owner of the Secure data of the failed secrets

  • in Cloud

    • navigate to Settings > General Configuration > User Management

    • navigate to Product access

    • ensure the user has Site access

Secure macros cannot be transformed if the Confluence administrator does not have Add page access to the target page where the Secret will be transformed to. This too will result in the error Migration is incomplete.

Run through the steps below

  • in server

    • find the original page of the Secure data of the failed secrets

  • in Cloud

    • navigate to the same page hierarchy as previous

    • enable Add page permission at Space settings for the user performing the migration