User Guide Cancel

Technical notifications

 

Adobe Acrobat Sign Guide

What's New

Get Started

Administer

Send, Sign, and Manage Agreements

Advanced Agreement Capabilities and Workflows

Integrate with other products

Acrobat Sign Developer

Support and Troubleshooting

The Adobe Acrobat Sign Technical Notifications are ordered below, with the current update at the top, and rolling back in time as you scroll down the page. 

 

Note:

This Technical Notifications page is regularly updated as new information becomes available, so its content is highly dynamic.

While the page is localized, the process takes time, which may result in localized versions differing slightly from the authoritative US English version.

For the most accurate and up-to-date information, we recommend referring to the US English page.

[Important] The next Adobe Acrobat Sign release is scheduled for February 11, 2025

Feature Release: Adobe Acrobat Sign – November 12th Release Completed

The release was completed to all shards with no downtime to any services.


[Important]
Adobe Acrobat Sign SSL Certificate updates in January, 2025

First Reported: December 2024

Current 

Adobe Acrobat Sign will rotate the Adobe Acrobat Sign SSL Certificate on January 22, 2025.

In addition, a new SSL certificate is being deployed to support the WAF network changes being made in January 2025This new certificate directly impacts access to the Acrobat Sign service and must be installed before the WAF goes online.

Action Required

  • Every customer account that explicitly secures network activity must include the new WAF SSL certificate in its list of stored certificates.
  • If you have custom-built integrations with Acrobat Sign using either the SOAP or REST APIs and if any of these integrations have ‘pinned’ the existing public key, no other action is required.
  • If you are using Acrobat Sign’s SSL certificates for SSO, or if you’re pinning the certificate itself (or using other methods), you can find the new Acrobat Sign SSL certificates in the Adobe Acrobat Sign System Requirements.
    • If your SSO configuration supports multiple public certs/chains, you can add the new certificates now and remove the old public cert/chain from your configuration after the January switch.
    • If your SSO does not support multiple public certs/chains, you will need to sync your SSL switch with Acrobat Sign on January 22, 2025.  

The new SSL certificates will be active on January 22, 2025.


[Important - Updated]
 Changes to the Adobe Acrobat Sign Network Infrastructure have been deferred until later in the first half of 2025

First Reported: September 2024 - Updated January 2025

Current 

To improve Adobe Acrobat Sign service security and robustness, we will roll out network changes to include a web application firewall (WAF) in the first half of 2025 (final dates to be determined; Bookmark this notice!). These changes will route traffic into Acrobat Sign application servers through the WAF service. This routing will be invisible to most customers. Usage will not interfere with access to Acrobat Sign from any Adobe clients or integrations.

Action Required

In most cases, this change will not affect customer integrations, as the Acrobat Sign API and API domain names will not change. However, the underlying IP addresses for the Acrobat Sign API endpoints will shift.

Integrations written to explicitly allow-list the outbound connections with the previously documented Acrobat Sign API ingress addresses will need to remove those legacy allow-listings before the WAF implementation. 


[Important]
 Disablement of the SOAP API from Adobe Acrobat Sign accounts is scheduled to start in February 2024

First Reported: June 2018 - Updated May 2024

Current

Action Required

All integrations and applications using the Adobe Acrobat Sign SOAP API must be migrated to the latest REST API V6 before the disablement date to ensure continued function.


[Important]
 Disablement of the SOAP API for Adobe Acrobat Sign Embedded Partners has been scheduled for March 1, 2025

First Reported: June 2018 - Updated May 2024

Current

Action Required

All integrations and applications using the Adobe Acrobat Sign SOAP API must be migrated to the latest REST API V6 before the disablement date to ensure continued function.


[Updated]
 Option to enable a mobile-friendly view of agreement fields for mobile recipients using a web browser.
To be added to Sandbox on December 11, 2024; Production on February 11, 2025

First Reported: November 2024 - Updated: December 2024

Current 


[New]
The Account and Group tab will be renamed to Admin and Group Admin starting with the April 2025 release

First Reported: November 2024

Current 


Customers with a Sandbox environment will be able to access the new Recipient experiences the first week of December 2024

First Reported: November 2024

Current 

The new recipient experience contains signing improvements for both desktop and mobile web browsers. This new experience is being rolled out over the first months of 2025 but will be available in the Sandbox environment in the first week of December 2024.


The webhookNotificationApplicableUsers parameter is to be removed from the Webhook payload in the March 2025 release.

First Reported: September 2024

Current 

The Webhook 2.0 infrastructure has been rolled out to all customers, and with that completed, signer notifications have been deprecated. As a result, the webhookNotificationApplicableUsers parameter of the webhook payload no longer provides any useful data and will be removed from all webhook payloads when the March 2025 release is deployed.

The sending userID and email can be found using the initiatingUserId and initiatingUserEmail parameters in the notification payload. 


Deprecation of the Adobe Acrobat Sign REST API v1-v4.
End of support and removal of legacy REST API versions on December 1, 2025.

First Reported: September 2024

Current 

Action Required

All customers using the API must update their APIs to utilize the version 6 endpoints as soon as possible to ensure uninterrupted availability. 


The new Request Signature environment will be promoted to be the default experience in the September 2024 release.
Switch links between Classic and New environments will be removed in the April 2025 release.

Note:

This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.

First Reported: March 2024 - Updated November 2024

Current 


The classic Compose page will be retired and removed from the commercial interface in the March 2025 release.

Note:

This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.

First Reported: June 2024

Current 


The classic Send in Bulk environment will be retired in March 2025.
Adobe Acrobat Sign's new
Send in Bulk environment became the default experience for all commercial accounts on April 9, 2024.

First Reported: March 2024

Current 


Classic reporting to be removed from service in the first half of 2025

First Reported: September 2022 - Updated March 2024

Current 


External source drives to be removed from support in the new Request Signature experience

First Reported: May 2024

Current 


Additional Resources


The Accept-Charset header will be removed from Webhook and Callback notifications in the November 2024 release

First Reported: August 2024

Removed from Current list: January 2025


Adobe Acrobat Sign Cookie Partitioning to be enabled in the November 2024 release.
Available in the Sandbox now.

First Reported: September 2024

Removed from Current list: January 2025


Custom Workflow Designer places a 100-character limit on labels for all new and existing workflow templates

First Reported: November 2024

Removed from Current list: January 2025

With the November 2024 release, the editable labels in the Custom Workflow Designer have been limited to 100 characters. This limit is evaluated when the workflow is created or updated.

Preexisting workflows that have labels over 100 characters can still be sent successfully, but if the workflow is updated, the label must be reduced to 100 characters or less before it can be saved. Offending labels are outlined in red for easy discovery.

New workflows will warn about the label limit before they are saved.

Action Required

It is recommended that admins with control over custom workflows open and review each workflow to ensure that they don't have errors on their template.

Archived Notifications

Listed by the date when the notice was removed from the current notice list, most recent to oldest.

Get help faster and easier

New user?