Question
Can pages signed with eSign be migrated (exported/imported) between separate Atlassian cloud sites
Background
-
eSign for Confluence signature data is stored as content properties within the pages in the site. (Nothing is stored outside or in eSign)
-
The signature data is digitally signed and linked to the specific confluence Page ID in the site. Any external modifications to the signature data, or if the signature data is artificially moved to a page with a different confluence page ID will trigger a verification failure on any active signatures. This is required for security and compliance with electronic signature regulations.
-
The PDF Signature Archive file, optionally attached to the page after finalizing, is a regular PDF file.
Cloud Export/Import
If Confluence Pages with Signatures are exported from Site A and imported to Site B, the following behavior would be expected.
-
On import the page contents and attachments would be created as a new page in the new Site.
-
Content properties would be including the eSign signature data
-
The new pages would have different Confluence Page IDs
-
The PDF Signature Archive attachments would continue to be accessible and contain the history of signatures from the old site.
-
Active signature data would fail verification (due to the change in page ID).
-
Imported pages (with signatures) could only have new signatures added after the Signature Admin > Remove All Signatures is run to reset the page and start clean with signatures in the new space.
Recommendations
If it is necessary to move Confluence pages with eSign Signatures between separate Atlassian sites, enable the PDF Signature Archive option (in App Settings) and Finalize all pages with Signatures. This will generate and attach the Signature Archive as a PDF Attachment on the page, providing a permanent immutable record of the signatures.
Once the page is on the new site, use Admin > Remove All Signatures for pages that need to be signed. Note that the PDF report will be retained.