 | eSign for Confluence |
Highlights
Data Processing Residency available for Europe
eSign for Confluence has added a new EU processing location. Customers now have the option to “Pin” their eSign app location to European Union or USA. Once pinned, the eSign server(s) in that location will perform all signature processing for that cloud site.
Note that eSign does not permanently store any end-user data outside of the Atlassian cloud. This change will have 2 key benefits:
For customers with EU compliance requirements, pinning the location to EU will ensure that signature data processing occurs with the EU.
Customers with Atlassian cloud sites located “closer” to the EU will notice faster response time when working with eSign as compared to the US hosted location.
See this Atlassian article for more information on Data Residency. https://www.atlassian.com/software/data-residency
Pinning apps is available within admin.atlassian.com
Application Residency and Diagnostics
To improve visibility, the eSign Global Settings page now displays the app current host, location and measured client browser latency.
Access from Confluence Administration > eSign for Confluence > eSign Global Settings
Webhooks for Confluence Automation
Automation rules such as adding custom labels, email or slack notifications, and other automation tasks can now be triggered by eSign Signature events.
eSign configuration includes webhooks for Signature Start, Invite, Execute (Sign) and Finalize.
Webhooks are compatible with and can trigger either Confluence or Jira Automation rules.
Webhook provides relevant page and signature data to the Automation engine.
See the Webhooks for Confluence and Jira Automation user guide for more information, and How to integrate Confluence Automation Rules with eSign Document Events for examples of Automation rule setup.
Change Log
2024-11-25
FIX Resolve issue with automated data residency migration between US and EU environments
2024-11-06
NEW Added Webhooks for Signature Event integration to Atlassian Automation rules. Configure the webhooks in eSign Global App Settings
TECH Extended support for customers using eSign with Atlassian custom domains.
2024-10-26
TECH Updates to use new Atlassian API’s.
2024-10-01
IMPROVED Signature Macro has new option to show signature date only. Default is to show Date and Time.
UX Signature Search macro can search within ancestor pages via CQL filter. Added documentation link and examples to show users how to configure this. See Signature Search Macro
TECH Improve performance of Confluence PDF export of pages containing live Signature Search macro.
TECH Improve logging and resilience for emails sent when some users have missing addresses.
2024-09-09
FIX Fix the display of invited users whose names contain apostrophes/quotes.
2024-07-10
TECH Improve automated recovery for app permissions on restricted pages.
2024-06-12
FIX Resolved issue where user titles applied while signing were not always saved for reuse on subsequent signatures.
2024-06-06
IMPROVED Data Residency Improvement to add support for automated migration of pinned client sites between US and EU/DE environments
2024-03-11
FEATURE Data Residency (Processing) Released for EU/DE regions in addition to US default location
2024-02-16
FIX Resolved issue where the Administrator Action > Remove All Signatures may not complete if an expected signature data property was missing
2024-02-08
FIX Resolved issue with application user accounts showing in the invite users list.
2024-01-24
FIX Resolved issue with unicode titles blocking pin reset.
.
 | eSign for Confluence |
RELEASED Dark Theme Support
eSign for Confluence now supports both the light and dark themes of Confluence cloud, providing a seamless experience for users using Confluence in either mode.
All eSign screens, dialogs and messages are now accessible and adapt to the current user theme.
Atlassian Confluence API Changes
This release includes a number API changes to address recent changes within the Confluence cloud platform.
Performance Improvements
In conjunction with the API changes, the eSign team has implemented a number of performance tuning improvements to allow signatures and other options to complete more quickly.
Inline Signature Verification
Inline verification of signatures has improved messaging to make it clear to users how many and which signatures have passed verification.
Additional Items
Security improvements including implementation of a Content Security Policy.
2023-12-11 Improved error messages on page restrictions that can block eSign app access.
2023-12-12 Resolved issue with invite email link being blank in certain situations.
2023-12-13 Resolved issue with storing unicode values in user profile API.
2023-12-13 Resolved issue with migrating global esign settings to new API.
2024-01-24 Resolved issue with unicode titles blocking pin reset.
2024-01-24 Resolved issue with application user accounts showing in the invite users list.
2024-02-08 Resolved issue where the reset pin link in popup expired pin message did not work.
2024-02-16 Resolved issue where the Administrator Action > Remove All Signatures may not complete if am expected signature data property was missing.
 | eSign for Confluence |
Signature Invite Improvements
Open Invites now show the time since the invite.
Incomplete (open) invites are now automatically cancelled on Finalize. This will help with housekeeping and remove “Pending Users” from the search screens showing old documents that are already signed. The Finalize audit comment will record these cancellations (if applicable).
More Signature Type Meanings
The limit on configurable Signature Type Meanings has been raised to 12. Configure additional Meanings in eSign App Settings.
Search Flags on Post-Signature Attachments
The Search page and eSign Search Macro now displays a warning flag for pages with new attachments added after signing.
Additional Items
Resolved issue with the search macro page size limits not being applied in all situations.
Security and technical library updates
Formatting updates to the PDF Signature Archive report
 | eSign for Confluence |
Additional Items
Security update for package dependencies
1. Issues
Resolved problem with exporting reports for pages containing comments not attributed to an account (e.g. anonymous).
2. Security
XSS hardening
Changes
Resolved problem with signature checksum verification (falsely) reporting a page was modified on certain long duration signature pages.
Improved notification message when a signature page with many signatures (e.g. > 70) exceeded the maximum size permitted by the Atlassian API.
PDF Signature Archive now only includes comments from after the current signature page was started to support customers that need to sign/archive multiple times on the same page.
Security
2022-07-06 - Various hardening and security improvements applied
Released March 12, 2022
1. Signature Search highlights updated content
To assist with signature verification, Search has been enhanced to highlight 
Confluence pages reported as updated by Confluence after the first signature was captured. This is an indication that the content may have been changed and should be reviewed and Signatures re-verified.
It is recommended to enable the automatic content locking after Signing (available in the Start Signatures dialog and via eSign Configuration) to prevent unintentional content edits after signing.
2. Signature Verification now displayed in dialog frame
For improved usability the signature verification report is now displayed within a dialog frame on the content page, instead of navigating to a new tab page. Save/Print is still available from the frame.
3. Faster Finalize with PDF Archiving
PDF Signature Archiving has been moved to background processing so that users do not have to wait for the archive to complete before receiving confirmation of Finalize. The completed Signature Archive report will be automatically attached to the Confluence page within ~30 seconds.
4. Additional Items
4.1 eSign for Confluence has achieved Atlassian Cloud Fortified Satus.
See details here: https://www.atlassian.com/trust/marketplace?source=app-listing-badge
4.2 eSign Support Documentation has moved
With this update eSign online documentation has moved to https://support.esign-app.com. All help links within the app now direct users to this new site.
1. Signature Search
This update adds comprehensive search capabilities; search for pages globally, by space or by user.
Search can be accessed from Apps > eSign Search, User Profile > My Signatures, Space Settings > Signatures, and/or the eSign Signatures Dialog.
The Search view displays Status (of Signatures), # of Signees, Invite Counts, as well as the users who have signed and the users who are waiting to sign.
Filter by Content text, Status (Open, Pending, Final) and User Role (Signed, Pending, or Owner).
2. eSign Search Macro
Search reports can now be embedded in any page to provide customized and reusable management reports. The search macro has additional options and can even include custom CQL clauses for advanced filtering.
3. Signing Pins can now be turned off
For customers that do not require the secondary authentication of a signing pin for regulatory compliance, the Pin Required feature can now be turned off.
Signature Pin is required by default; configure this setting under Manage Apps >
eSign > Configure.With the Pin feature off, users will no longer be prompted to enter a pin to Execute Signatures.
4. Additional Items
4.1 eSign is FREE for Small Teams
eSign is happy to announce that eSign is now free to use for teams of up to 10 users.
4.2 Security Hardening
As part of our continuous efforts to maintain a robust and secure app, the eSign for Confluence team completed a comprehensive security review with updates applied where possible.
Note that eSign does not store any customer, user or signature data. All persistent Signature data is stored within the Confluence cloud infrastructure. These signature records are cryptographically signed to prevent/detect unauthorized modification.
4.3 Pending Signatures
The Signatures Dialog now displays the PENDING label if there are active invites waiting to be signed.
Jan 2022 Update RELEASED JAN 15
#1 Signature Search
This update adds comprehensive search capabilities; search for pages globally, by space or by user.
Search can be accessed from Apps > eSign Search, User Profile > My Signatures, Space Settings > Signatures, and/or the eSign Signatures Dialog.
The Search view displays Status (of Signatures), # of Signees, Invite Counts, as well as the users who have signed and the users who are waiting to sign.
Filter by Content text, Status (Open, Pending, Final) and User Role (Signed, Pending, or Owner).
#2 eSign Search Macro
Search reports can now be embedded in any page to provide customized and reusable management reports. The search macro has additional options and can even include custom CQL clauses for advanced filtering.
#3 Signing Pins can now be turned off
For customers that do not require the secondary authentication of a signing pin for regulatory compliance, the Pin Required feature can now be turned off.
Signature Pin is required by default; configure this setting under Manage Apps >
eSign > Configure.With the Pin feature off, users will no longer be prompted to enter a pin to Execute Signatures.
#4 Additional Items
4.1 eSign is FREE for Small Teams
eSign is happy to announce that eSign is now free to use for teams of up to 10 users.
4.2 Security Hardening
As part of our continuous efforts to maintain a robust and secure app, the eSign for Confluence team completed a comprehensive security review with updates applied where possible.
Note that eSign does not store any customer, user or signature data. All persistent Signature data is stored within the Confluence cloud infrastructure. These signature records are cryptographically signed to prevent/detect unauthorized modification.
4.3 Pending Signatures
The Signatures Dialog now displays the PENDING label if there are active invites waiting to be signed.
Dec 2021 Update
Security Advisory on Log4j
Digital Rose has reviewed and confirmed that the eSign infrastructure is not vulnerable to the Log4J security issue (CVE-2021-44228). The implicated log4J library is not included in any client side or server side components.
For more information on Atlassian Cloud’s overall impact of this issue, see: https://community.atlassian.com/t5/Trust-Security-articles/Atlassian-s-Response-to-Log4j-CVE-2021-44228/ba-p/1886598
Nov 2021 Update
#1 Signature Start Workflow and Page Owners
This update adds additional controls to the eSign process by identifying a new role for Signature Page Owners. Signature management functions such as invite and administration are restricted to the identified owners of each page. Owners are set at the beginning of the process when Signatures are Started.
The user who Starts eSign for this page is by default an owner; they can optionally add additional users.
Owners can Invite and Administer signatures for the page. Space administrators can act as Owners.
Designated owners are displayed in the footer of the Signature panel, and are included in the Signature invite email.
#2 Signatures by Invite Only
eSign now supports restricting pages to only be signed by Invitees. This option can be selected on the Open Signatures dialog (Start).
Only users who are invited to sign the page will be able to sign.
Re-signing will be allowed for previously invited users.
#3 Signature Pin Reset Usability and Security Improvements
Simpler and faster Signature Pin resets now occur directly via email as users will receive a new Pin that can be used immediately to sign.
Pin minimum length has been extended to 6 digits and Pins will expire after 180 days.
Users may (still) update the Pin to a preferred value via eSign User Settings.
Signature Reset can be requested in the Execute Signatures or eSign User Settings page.
#4 eSign Macro Grouping
The eSign Macro can now filter by Meanings to allow separate signing blocks on one Confluence page. For example, Approvers and Invitees can show in one block, and Read & Understood signatures can show in a separate eSign Macro on the same page.
#5 Content VersionÂ
At the time of signing, the Confluence content version is captured and displayed for each signature and displayed for page export and the PDF Archive.
The Content Version signed is also visible in the PDF Signature Archive and in pages with the eSign Macro exported to Word/PDF.
Note that Confluence does not change content version numbers when attachments are modified. Continue to use the eSign Signature Verification report to confirm neither page content nor attachments were modified since signing.
#6 Additional Items
Invite Dialog Usability
To assist with larger team invites, the Invite Dialog now shows a running counter of how many users are selected for the invite. Note a maximum of 50 users may be invited at a time.
eSign Update Notification
To ensure that users are aware of significant eSign changes in this update, a What Is New help message will display in the Signature Panel the first time a user accesses it.
Click the NEW changes label in the footer to access this info at a later time.
Sep 2021 Update
#1 PDF Signature Archives
eSign now supports automated generation of a PDF Signature Archive as a point in time snapshot of the Finalized Signature content. These archives include Confluence page information, as well as all Attachments, Comments, and Signatures. All Signatures are re-verified as well.
The Archive PDFs are added as attachments to the Confluence page when Signatures are finalized. Users can view/download these archives on demand as needed for reference, offline copy, audits, etc.
See PDF Signature Archives for examples and additional information.
#2 View and Download All Attachments
eSign has now made it easier to access Confluence Attachments by adding links to the Signature dialog. This allows users to quickly view attachments, as well as provide a one-click Download All option to download all page attachments (including the new Signature Archive) as a single .zip file.
Aug 2021 Update
#1 Signature Flexibility
eSign now supports users signing multiple times on the same page with distinct meanings. Repeated signatures with the same meanings will continue to automatically void the previous signature. (Voided signatures can be viewed from the more (…) menu in the eSign Content dialog.)
#2 Pending Signature Label
To make it easier to find and manage pages with Pending Signatures (Users have been invited but have not Signed yet), eSign will now add an esign-pending label to any page with 1 or more pending signatures. This label can be used as a search term within confluence and the (built-in) content report macro. For additional information on searching labels in Confluence Cloud, see the following resources:
https://support.atlassian.com/confluence-cloud/docs/use-labels-to-organize-your-content/
https://support.atlassian.com/confluence-cloud/docs/insert-the-content-report-table-macro/
Jun 2021 Update
#1 User Experience Improvements
Byline Signature summary will now show invite completion as a ratio X/Y.
eSign Invite replies are now automatically addressed to the Invitor (previously replies would be sent to the eSign support desk).
eSign Invite email format has been refreshed.
#2 Technical Updates
Cache duration of certain static assets has been extended.
Update Atlassian connect library for improved security.
May 2021 Update
#1 Read Confirmation workflows
eSign now supports tracking of Read Confirmations for reference material, corporate policies, etc. Read Confirmations are fully-compliant electronic signatures.
The Meaning for each Signature can now be selected from a configurable picklist. Default values are “Approval”, and “Read & Understood”. Administrators can modify this list in App Settings.
A new Read Confirmation blueprint has been added to help get started.
#2 eSign Macro - Compact View
The eSign macro displayed in-page can now be configured between Traditional signature view and a new Compact view. This new view option can be used with any type of Signatures, on any confluence content.
#3 User Experience Changes
Finalize signatures now includes an inline confirmation check.
Signature status/meanings columns condensed to display Signature meanings within a status lozenge.
The Signature dialog is now dynamically rendered client side for improved responsiveness.
Signature Certificate renamed to Signature Verification Report and opens in a new tab.
Signature dialog toolbar simplified for Finalized pages.
#4 Security
eSign can now work with content that is only visible/editable to a subset of users through Confluence page restrictions. This change requires the “Act As User” privilege to be available to the App.
For improved security, the personal Signing Pins are now locked out after a number of invalid attempts. At this point Pins will need to be reset via e-mail.
Apr 2021 Update
#1 Security and Maintenance
April update of eSign for Confluence included internal maintenance and security improvements. No functional changes.
Mar 2021 Update
#1 eSign is now faster with Global CDN
eSign for Confluence static resources are now distributed through the AWS Cloudfront Content Delivery Network (CDN). This will improve Signature display performance and reduce latency for eSign users as the CDN will cache shared resources globally.
#2 Opt-in Content Locking
With this update the AutoLock feature is displayed on the Execute Signature dialog so users can see if the content (page and attachments) will be locked upon signing. Content AutoLock can be enabled/disabled from the eSign App Configure page.
If AutoLock is not enabled, users may still optionally check this box to lock this content with their signature. Space Administrators have access to additional Lock/Unlock functions in the more (…) menu if necessary to manually adjust locked content.
#3 Other Changes
A "New Recent Updates" flag will display in the footer of the eSign Content dialog when a recent eSign update is detected. Users may click the flag to access the latest update documentation.
Instructions improved on the Document Approval and Training Blueprints.
TIP: Quickly find eSign blueprints by searching for “Signature” in the Confluence Create page.Signee Title is now displayed on the Verification Report
Feb 2021 First Release
#1 Electronic Signature Engine
Extending the core Electronic Signature engine from Jira to Confluence content.
Apply Electronic Signatures to any confluence content
Signature verification to certify that the signed confluence content and attachments have not changed
Invite other users to sign and manage the signature process
#2 Confluence Specific Extensions
Allow and persist personal signing Pins within Confluence environment.
Supports optional autoLock of content and attachments to prevent editing once signing has commenced.
Add eSign Status tracking to show Open and Finalized signature pages
#3 Confluence Macros Blueprints
Includes inline macro to display and allow Signing from within pages.
Includes sample and extensible confluence eSign blueprints for Document Approval and Training Attendance forms.
We Love Feedback
Please share your eSign experiences with us. Let us know what you like, what you don’t and what features would make it better.
Leave feedback via the Contact eSign button in the Atlassian Marketplace