First Reported: August 2024
Last updated on
Mar 26, 2025
The Adobe Sign Technical Notifications are ordered below with the most recent update at the top, and rolling back in time as you scroll down the page.
|
|
Removed from Current list: January 2025 |
|---|
The legacy Accept-Charset header will be removed from all Webhook and Callback notifications with the November 2024 release.
All customers that rely on this header for any reason should refactor their code to account for it's absence.
|
First Reported: September 2024 |
Removed from Current list: January 2025 |
|---|
|
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.
|
First Reported: November 2024 |
Removed from Current list: February 2025 |
|---|
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.
|
First Reported: December 2024 |
Removed from Current list: February 2025 |
|---|
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 2025. This 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.
|
First Reported: September 2024 - Updated February 2025 |
Removed from Current list: March 2025 |
|---|
To improve Adobe Acrobat Sign service security and robustness, we will start to roll out network changes to include a web application firewall (WAF) in February 2025. 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
None.
This change will not affect customer integrations, as the Acrobat Sign API and API domain names will not change. This solution is backward compatible with the published IP ranges.
Customers who have updated their security devices don't need to revert or make any other changes.
The current update schedule is:
- Production Sandbox updates February 24, 2025.
- Production shards: IN1, JP1, AU1, and SG1 will update March 3, 2025.
- Production shards: NA2, NA3, and EU2 will update March 6, 2025.
- Production shards: NA1, NA4, and EU1 will update March 11, 2025.
-
Ingress and Egress Access to Acrobat Sign
Acrobat Sign is no longer retiring the list of server ingress IP addresses as previously announced.
The server ingress and egress IP addresses, as documented on the System Requirements for Acrobat Sign page, will remain viable. -
Why is Acrobat Sign making these Changes?
The use of a WAF improves Acrobat Sign's protection against harmful traffic and helps us better address security, robustness, and compliance requirements.
-
I have a custom integration into Acrobat Sign. Will my application be affected?
No, we don't expect any integrations to be negatively impacted.
-
Are there new IP address lists that can be substituted?
No.
The information on the System Requirements for Acrobat Sign page remains accurate. -
My organization has implemented network filtering using Acrobat Sign's published domain list for traffic from our corporate network. Are we affected?
No.
The network changes described here do not impact Acrobat Sign's domain list, as documented on the System Requirements for Acrobat Sign page. Domain-level filtering is unaffected. -
My organization employs IP address validation for email delivery from Acrobat Sign servers. Are we affected?
No.
The IP ranges for outbound mail relays, as listed on the System Requirements for Acrobat Sign page, are not changing. -
My organization has configured our Acrobat Sign account to restrict access to our own IP addresses. Are we affected?
No.
Acrobat Sign can be configured to validate incoming traffic against customer-chosen IP addresses, as described on the Restrict access to your account using IP address ranges page. Such usage will not be affected by this change. -
My organization has implemented network filtering using Acrobat Sign's published list of ingress IP addresses. Are we affected?
No.
The new WAF configuration is backward compatible with the existing network architecture, so no additional tuning of your security devices should be required.
Note:Note that this refers to IP-level filtering for the environment hosting your application. Domain-level filtering is not affected.
-
I'm using the Salesforce integration with explicitly configured IP allow-listing. Do I need to do anything?
No.
The WAF installation requires no changes for existing Salesforce installations at this time.
The existing configuration/process, as described in the help documentation, remains the same, and administrators should follow all IP allow-listing steps.
ISV and Embed Partners should contact their Success Manager for any further questions.
|
First Reported: November 2024 - Updated: January 2025 |
Removed from Current list: March 2025 |
|---|
Senders can provide an additional view of agreements for mobile recipients that lists only the field within the agreement available to the recipient.
Senders can arrange the field list as they like, and group fields into logical sections to help the signers move through the field input with a minimum of scrolling.
Recipients have the option to view the mobile-friendly fields list or the original PDF view with the fields placed within the document content.
This feature is scheduled to be released:
- To be deployed on the Sandbox environment on December 11, 2024
- To be deployed on the Production environment on March 4, 2025
|
First Reported: May 2024 |
Removed from Current list: March 2025 |
|---|
The option to use an external drive for uploading files will be limited to OneDrive only in the new Request Signature experience.
It's recommended that customers who use other options for file upload use the vendor-specific application to provide a networked drive that can be accessed through the native file picker on the user's local system.
- Dropbox: https://www.dropbox.com/desktop
- Google Drive: https://support.google.com/drive/answer/10838124
- Box: https://support.box.com/hc/en-us/articles/360043697194-Installing-Box-Sync
- Acrobat/Document Cloud: https://www.adobe.com/acrobat/hub/share-sync-pdfs.html
