First Reported: August 2023
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.
[Important] The next Adobe Acrobat Sign release is scheduled for September 26, 2023
This will be a minor patch release to resolve a number of customer-found defects and apply any optimization/security patches as needed.
The Sandbox environment will adopt these patches four weeks prior to the scheduled release. A listing of the resolved customer issues will be published at that time and updated 14 days prior to release.
Feature Release: Adobe Acrobat Sign – August 22nd Release Completed
The release is complete to all shards with no downtime to any services.
|
Current |
---|
With the September 2023 release, the customer interface for viewing an agreement is moving the PDF controls from under the document to the right side of the document.
Additionally, an option to view two pages has been added.
The Search option isn't included in the PDF controls at this time, but users can employ Ctrl/Cmd + F to search the document content.

Signing the agreement (when a signature is requested of the user) isn't impacted by this change.
First Reported: September 2023 |
Current |
---|
Adobe Acrobat Sign will rotate the Root and Intermediate SSL Certificates on the morning of March 1st, 2024.
There is no change to the public key, underlying cryptographic protocols, or scheme.
ACTION REQUIRED
Use of the public key
- 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 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 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 April switch.
- If your SSO does not support multiple public certs/chains, you will need to sync your SSL switch with Acrobat Sign on March 1st, 2024.
The new SSL certificates will be active on March 1st, 2024.
First Reported: August 2023 |
Current |
---|
There is a known issue regarding not being able to move signature and text fields in the drag-and-drop authoring environment when using new Chrome and Edge versions. When the field is placed, it cannot be click-dragged to a new location on the agreement.
The impacted browser versions are:
- Chrome
- 116.0.5845.96
- 116.0.5845.97
- 116.0.5845.111
- Microsoft Edge 116.x
Current workaround options are:
- Use a different browser.
- If no other browser is available:
- In classic authoring, select the grab handle to the left of the field to drag/drop.
- In new authoring, select the field, then use the keyboard (Cmd + Shift + arrow keys) to move the fields.
First Reported: September 2022 |
Current |
---|
The November 2022 release for Acrobat Sign includes two updates to the new reporting environment:
- Scheduling and distribution of reports and data exports
- Addition of previously missing columns in data exports
This release brings the new reporting interface into feature parity with the classic reporting structure and begins the process of adding new capabilities.
All future development for reporting features will be built on the new experience only. Consequently, the classic reporting interface will be removed from service in November, 2023.
All users and administrators are encouraged to migrate their reporting tasks to the new experience as soon as possible.
First Reported: June 2023 |
Current |
---|
Acrobat Sign support for Microsoft SharePoint on-premises is set to end by October 22, 2023. On that date, the integration will no longer be able to send or process agreements.
Agreements previously sent for signature from the integration will continue to be available for recipients to sign, but the completed documents will not be saved back to SharePoint. Users will need to manually download a copy of the final executed agreement and upload it to their SharePoint site if they wish to save a copy in SharePoint.
Advanced workflow features (e.g., data mapping between SharePoint lists and Acrobat Sign workflow templates) will no longer be available. However, the underlying data will not be affected. Completed agreements and other data stored on your SharePoint instance or with Acrobat Sign will not be affected.
It's recommended that impacted customers remove the Acrobat Sign plug-in from their SharePoint on-premise instance and replace it with other Acrobat Sign integrations, such as Adobe Acrobat Sign for Microsoft Sharepoint Online or the integration with Microsoft Power Automate.
This change doesn't affect the integration of Adobe Acrobat Sign with Microsoft SharePoint Online. This end-of-service notification applies only to the on-premises deployments of Microsoft SharePoint Server.
Unsanctioned page modifications may be disabled
First Reported: February 2023 |
Current |
---|
Modifications to HTML pages delivered by Adobe, except for those enabled by published APIs and features, are unsupported. Such modifications may interfere with the functionality of Acrobat Sign. Adobe may, at any time, make technical changes that disable the function of any non-Adobe-sanctioned HTML page modifications.
If your use of Acrobat Sign currently relies on modifying HTML from Acrobat Sign using browser extensions, HTTP proxies, or any other means not enabled by Adobe published APIs and features, you should migrate away from these as soon as possible to avoid disruption.
This statement applies to any mechanism by which such modifications may be made, such as browser extensions and browser configurations which allow HTTP proxies to modify page content.
Additional Resources
- Community forums
- Weekly Training - Weekly Webinar covering training topics for new users and administrators
- Adobe Sign Innovation Series - Monthly Webinar covering the hottest topics in the Adobe Sign space
Past Notifications
Adobe Acrobat Sign search service update for the NA2 environment scheduled Saturday, September 2, 2023
First Reported: August 2023 |
Removed From Current List: September 2023 |
---|
Adobe Acrobat Sign updated to the search service on the NA2 server environment starting in the afternoon of Saturday, September 2nd, and completing the morning of Sunday, September 3rd.PST. During the upgrade, users on the NA2 shard may experience a delay in observing their latest agreement updates/additions on the Manage page.
This activity will NOT impact
- Logging in to the application
- Sending new agreements or signing agreements that are in flight
- Creating new forms or signing active forms
- Using workflows or creating new workflows
Legacy TLS cipher suites were removed from service on July 18th, 2023
First Reported: March 2023 |
Removed From Current List: September 2023 |
---|
To maintain a strong level of security within the Adobe Acrobat Sign service, several legacy TLS ciphers that use static keys or the SHA-1 hash function will no longer be supported after July 17, 2023.
Customers using legacy ciphers should update the O/S, framework, or application code to use one of the supported TLS ciphers before July 18, 2023, to ensure uninterrupted service use.
After July 17, 2023, any application attempting to connect to an Acrobat Sign endpoint with a legacy cipher suite will fail.
Legacy cipher suites being removed from service:
IANA Name | OpenSSL Name |
TLS_RSA_WITH_AES_128_GCM_SHA256 | AES128-GCM-SHA256 |
TLS_RSA_WITH_AES_256_GCM_SHA384 | AES256-GCM-SHA384 |
TLS_RSA_WITH_AES_128_CBC_SHA256 | AES128-SHA256 |
TLS_RSA_WITH_AES_256_CBC_SHA256 | AES256-SHA256 |
TLS_RSA_WITH_AES_128_CBC_SHA | AES128-SHA |
TLS_RSA_WITH_AES_256_CBC_SHA | AES256-SHA |
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA | ECDHE-ECDSA-AES128-SHA |
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA | ECDHE-RSA-AES128-SHA |
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA | ECDHE-ECDSA-AES256-SHA |
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA | ECDHE-RSA-AES256-SHA |
Supported cipher suites:
IANA Name | OpenSSL Name |
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | ECDHE-ECDSA-AES128-GCM-SHA256 |
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | ECDHE-RSA-AES128-GCM-SHA256 |
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | ECDHE-ECDSA-AES256-GCM-SHA384 |
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | ECDHE-RSA-AES256-GCM-SHA384 |
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 | ECDHE-ECDSA-AES128-SHA256 |
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 | ECDHE-RSA-AES128-SHA256 |
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 | ECDHE-ECDSA-AES256-SHA384 |
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 | ECDHE-RSA-AES256-SHA384 |
Adobe Acrobat Sign search service updated for the NA1 environment on Sunday, August 20, 2023
First Reported: August 2023 |
Removed From Current List: September 2023 |
---|
Adobe Acrobat Sign is planning an update to the search service on the NA1 server environment during the early morning hours of Sunday, August 20th EST. During the upgrade, users on the NA1 shard may experience a delay in observing their latest agreement updates/additions on the Manage page.
This activity will NOT impact
- Logging in to the application
- Sending new agreements or signing agreements that are in flight
- Creating new forms or signing active forms
- Using workflows or creating new workflows
First Reported: October 2022 - Updated: July 2023 |
Removed From Current List: September 2023 |
---|
On November 8th, 2022, Acrobat Sign delivered an improved version of webhooks infrastructure (referred to as “webhooks 2.0”).
- New customer accounts created after November 8th, 2022, are automatically built with webhooks 2.0 enabled.
- The Sandbox environment will be updated on May 2nd, 2023.
- Accounts existing before November 9th, 2022, are to be migrated to the webhook 2.0 environment per the below schedule.
- Accounts in the Adobe Acrobat Sign for Government environment will be updated to Webhooks 2.0 on a future (undecided) date.
Launch date | Environment |
---|---|
02 May | Sandbox |
07 June | JP1 |
07 June | SG1 |
14 June | IN1 |
14 June | AU1 |
21 June | NA4 |
21 June | EU2 |
12 July | NA1 |
12 July | EU1 |
20 July | NA2 |
20 July | NA3 |
Webhooks 2.0 supports all the features of classic webhooks with one caveat. Classic webhooks configured for the user, their group, or their account, delivered notifications to all participants of an agreement. In webhooks 2.0, ONLY the sender, sender’s group or account will receive notifications. In other words, notifications are no longer sent to all participants of an agreement.
Note that all future webhook enhancements will ONLY be delivered on webhooks 2.0.
Current customers can try webhooks 2.0 on a Trial, Developer, or Sandbox account via Adobe’s Insider Access program starting November 8th.
The migration is expected to be seamless for all customers. However, customers who have strict network security policies in place will require new IP addresses to be configured in accordance with https://helpx.adobe.com/sign/system-requirements.html.
If you have any questions, reach out to your success manager or the support team.
First Reported: May 2023 |
Removed From Current List: September 2023 |
---|
In the July 2023 release, all accounts that have enabled Custom Send Workflows for their administrators will automatically be enabled with workflow designer access for all users.
Users can access the workflow designer through the Workflows tab in the top navigation bar and the Create reusable workflows tile on the Home page.
Unless the option to allow sharing of workflows is enabled, users will only have the authority to create workflows for their personal use.
The setting to allow sharing is not going to be changed.
Administrators that would like to remove workflow designer access from their users can disable the feature (at the account or group level) by navigating to Account Settings > Global Settings > Custom Send Workflows.
First Reported: June 2023 |
Removed From Current List: September 2023 |
---|
Throttling is being applied to REST /search API calls - All /search API calls are subject to volume throttling at the rate of:
- No more than 1000 calls per minute.
- No more than 2500 calls per hour.
- No more than 7200 calls per day.
Throttling will begin after the July 18th release is completed.
Administrators should file a support request to elevate the volumes if needed.
First Reported: April 2023 |
Removed From Current List: July 2023 |
---|
The Acrobat Sign release scheduled for May 2023 included availability of the Microsoft Power Automate integration for all accounts with an enterprise license.
Access to discover this feature via the Workflows tab and Home page access points is enabled by default for all users.
Using these access points, users are able to discover the value of Power Automate, and request access to the integration from their administrators.
The ability to create and use workflow is available until explicitly enabled by the account administrator.
Controls to disable user discoverability can be found in Account Settings > Global Settings.
First Reported: April 2023 |
Removed From Current List: July 2023 |
---|
The Acrobat Sign release scheduled for May 2023 included availability of the Microsoft Power Automate integration for all accounts with an enterprise license.
Access to discover this feature via the Workflows tab and Home page access points is enabled by default for all users.
Using these access points, users are able to discover the value of Power Automate, and request access to the integration from their administrators.
The ability to create and use workflow is available until explicitly enabled by the account administrator.
Archived Notifications
Listed by the date when the notice was removed from the current notice list, most recent to oldest.
Влезте във вашия акаунт