Adobe Sign Technical Notifications 2019-2020

Technical Notifications for 2019 - 2020

End of Service of RC4 Encryption for Adobe Sign generated PDFs

In January 2021 Adobe Sign will end the use of RC4 encryption in the Adobe Sign application and transition all accounts using RC4 to AES-128 Encryption.

Existing PDFs will remain unaffected by this change.

Adobe Sign deprecated the use of the 128-bit RC4 encryption method early in 2020 as support for the RC4 cipher option is no longer considered to be secure.

• The use of this cipher is to be eliminated in January 2021
• Adobe Sign will continue to offer the AES-128 and AES-256 cipher, which are both very strong, industry-standard options

ACTION REQUIRED:

None.

• Accounts configured for RC4 PDF encryption will have that setting upgraded automatically to AES-128
• Accounts configured for AES-128 or AES-256 encryption will remain the same

Access to Adobe Sign Support is changing: September 2020

The process for contacting Adobe Sign Support is changing two elements in September 2020:
Note: If you submit cases via the Adobe Admin Console this process will remain the same.

• Email is no longer supported for creating new cases - The decision to remove email support has been made to serve our customers more efficiently. Creating cases through an authenticated process ensures that Support can act on the request knowing it has been submitted by an authorized party for the customer organization.
• All cases must be submitted via an Admin. End-users must contact their group, privacy, or account admin to submit new support requests.

New SSL Certificate Available -
Going into effect October 8th, 2020

Adobe Sign is releasing a new SSL Certificate on October 8th, 2020.
There is no change to the public key, underlying cryptographic protocols, or scheme.

The new certificate is available by downloading it from Adobe Sign System Requirements.

ACTION REQUIRED

Use of the public key
If you have custom-built integrations with Adobe 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’re pinning the certificate itself or using other methods, you can find the new Adobe Sign certificate in the Adobe Sign System Requirements.

The new SSL certificate will become active on October 8^th, 2020.

Adobe Sign for Dynamics 365: Upgrade to version 9.2

A new version of Adobe Sign for Dynamics 365 has been released.

Dynamics admins can upgrade the existing app via the admin Settings > Solutions  

Adobe Sign for Microsoft Power Automate Actions updated to REST v6

The Adobe Sign for Power Automate 3.0 update introduces new REST v6 Actions that are intended as replacements for existing actions of the same name. Legacy Actions will be hidden and are deprecated by January 2021.

REST v6 API update: Additional attributes for multiple endpoints

As part of the July 2020 release, several of the REST v6 API endpoints are getting additional attributes:

New Release: Adobe Sign September 2020

The Adobe Sign September 2020 product release has completed with no downtime.

This product release includes new features and feature enhancements for administrators and end-users.

Planned “End of Service” for the Archive feature

The Archive feature is scheduled to be removed from the Adobe Sign system when the new Home and Manage pages are fully deployed and in service. This includes both direct upload and email to archive.

Users that have content in their Archive will still be able to view and access that content on the new Manage page, but new content may not be added. 

ACTION REQUIRED

No action is required. 

The ability to upload new content to the Archive section will be disconnected when the account migrates to the new Home/Manage page structure.

Planned “End of Service” for the Access Code feature

The legacy Access Code feature is scheduled to be removed from the Adobe Sign system when the new Home and Manage pages are fully deployed and in service. 

Users that have processes leveraging the Access Code should contact their Success Manager to discuss alternate methods to fulfill their business requirements.

ACTION REQUIRED

Customers that rely on the Access Code should contact their Success manager directly to discuss their signature flow requirements.

Limited Manage page availability on the evening of October 3rd PDT

Adobe Sign is planning an update to the search service during the evening of October 3^rd Pacific time.  There will be limited access to the manage page during this time and users may experience a maintenance message. 

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

The maintenance windows are planned regionally in order to have the smallest impact to active use as possible. Note: perceived impacts will be much shorter than these windows.

The planned maintenance windows for each region:

• APAC : 7:30 am – 8:30 am on Oct 4^th (3 pm – 4 pm PDT on Oct 3^rd)
• India: 4:30 am – 5 am on Oct 4^th (4 pm – 4:30 pm PDT on Oct 3^rd)
• Europe: 2 am – 3 am on Oct 4^th (5 pm – 6 pm PDT on Oct 3^rd)
• US (East): 11 pm – 12 am on Oct 3^rd (8 pm – 9 pm PDT on Oct 3^rd)
• US (West): 9 pm – 9:30 pm on Oct 3^rd

New Release: Adobe Sign July 2020

The Adobe Sign July 2020 product release has been completed.

This product release includes new features and feature enhancements for administrators and end-users.

No downtime was experienced during the release. 

Adobe Sign for SharePoint Online: Upload limit increased to 10MB

The upload limit for Adobe Sign for SharepPoint Online customers has been improved from 5MB to 10MB.

All customers gain the increase. No action is required, the update is in-place.

Adobe Sign for SharePoint Online: Seamless user provisioning

Seamless user provisioning is available to all Adobe Sign for SharePoint Online customers. Version does not matter.

SharePoint Administrators have a new option that grants access to the Adobe Sign integration automatically for any user assigned the default Edit permission for your SharePoint site.

Adobe Sign icon and font change

The August 2020 release includes a change to the Adobe Sign icon as well as the fonts used throughout the application.

Customers that use any type of robotic process automation (RPA) should be aware of this change in case it impacts how their automation functions.  

Adobe Sign does not support RPA, but it's understood that some customers may use it to automate common processes. 

If RPA is part of a customer's automation strategy they should be prepared to test and repair their existing RPA suites during this release time frame.

Contact your success manager if you have any questions.

Security Notice: Adobe Sign is ending support for older API authentication models in June 2020

Adobe is committed to providing safe and secure product experience for our customers by adhering to the latest industry standard security protocols. As a part of that process, Adobe Sign is ending support by June 2020 for older API authentication models that allowed sending username and password in the API call.

IMPACT

Clients currently using the older authentication model will need to move to the newer OAuth-based authentication. 

ACTION REQUIRED

• Customers using an integration should upgrade to the latest version. Refer to reference guides for all the latest Adobe-built partner integrations.
• Customers who have built their own custom integration with Adobe Sign will need to update to the latest OAuth-based authentication. For more details, please refer to this Migration Guide. 
  
• Mobile users will need to upgrade to the latest version of the Adobe Sign app for iOS & Android.

New Release: Adobe Sign March 2020

The Adobe Sign March 2020 product released March 18th.

This product release includes new features and feature enhancements for administrators and end-users.

No downtime was experienced during the release. 

Footer link to the Adobe Privacy site is to be removed from the Web interface

In the March 2020 release, the link to the Adobe privacy site in the web page footer was removed.

New Release: Adobe Sign for SharePoint Online v2

The latest version of Adobe Sign for SharePoint supports web form functionalities to help businesses collect data and e-signatures at scale.

SharePoint admins can upgrade the existing app from previous versions to version 2.0 via AppSource.

End of life for Adobe Sign for SharePoint Online Workflow - March 1st, 2020

The Adobe Sign for SharePoint Online Workflow package is being fully decommissioned and will stop functioning on March 1st, 2020.

Customers that leverage Workflows should migrate their processes to the Power Automate solution.

Throttling limits go into effect for Agreement processing

Throttling for agreement generating processes has been enabled for all accounts.

Please refer to the FAQ for specifics on the throttling process.

Chrome browser alert

The Chrome browser is updating to v80, and that update brings improved security around cookies.

These security updates demanded changes to our code that may impact older (unsupported) versions of the Chrome browser (v66 and older).

Customers that notice new UI errors/bugs should first check their browsers to ensure they are running a modern (supported) version of the browser, and update if they are not.

For more information please refer to the following articles:

• Google status updates for the "same site" cookie issue: https://www.chromium.org/updates/same-site 
• Google Chrome Schedule: https://www.chromestatus.com/features/schedule
• "Same Site" cookie issue explained: https://web.dev/samesite-cookies-explained/

New I-9 for 2020 added to the Adobe Sign Library

The new IRS I-9 (2020) form, entitled I-9 2020 (Employment Eligibility Verification), has been added to the Adobe Sign library.

ACTION REQUIRED

The new I-9 form template has a new libraryDocumentId. If you use the existing template’s libraryDocumentId in your applications, you will need to update it.

The 2019 version is to be removed from the system in May 2020.

Any application/API using the legacy (ver 2019) form must be updated before May 1^st to ensure no disruption to successful service.

To find the libraryDocumentId in an API-enabled account:

1    Log in as an Account Admin

2    Click on the Account tab > Adobe Sign API > API Information > click the link: REST API Methods Documentation

3    In the GET /libraryDocuments section, click the OAUTH ACCESS-TOKEN button 

a. Enable the library_read:self scope

4    Click the Try it out! button

5. In the Response Body, locate the new I-9 2020 (Employment Eligibility Verification) form template (not ver. 2019) to see the libraryDocumentId value. 

New W-4 for 2020 added to the Adobe Sign Library

The new IRS W-4 (2020) form, entitled W-4 2020 (Employee's Withholding Certificate), had been added to the Adobe Sign library.

ACTION REQUIRED

The new W-4 form template has a new libraryDocumentId. If you use the existing template’s libraryDocumentId in your applications, you will need to update it.

The 2019 version is to be removed from the system in May 2020.

Any application/API using the legacy (ver 2019) form must be updated before May 1^st to ensure no disruption to successful service.

To find the libraryDocumentId in an API-enabled account:

1    Log in as an Account Admin

2    Click on the Account tab > Adobe Sign API > API Information > click the link: REST API Methods Documentation

3    In the GET /libraryDocuments section, click the OAUTH ACCESS-TOKEN button 

a. Enable the library_read:self scope

4    Click the Try it out! button

5. In the Response Body, locate the new W-4 2020 (Employee's Withholding Certificate) form template (not ver. 2019) to see the libraryDocumentId value. 

Note: Customers that prefer to manage the tax form within their account library can download a fully tagged PDF here.

If you need more information, please contact your Customer Success Manager.

Adobe Sign for Salesforce v21.5.11

Adobe Sign for Salesforce customers must upgrade to the latest version as soon as possible. 

Adobe Sign for Salesforce v21.5.11 is required as a pre-requisite for all new Adobe Sign for Salesforce versions going forward.

Action required

Please upgrade before the end of November 2019. To upgrade:

• Read the Release Notes
• Download version 21.5.11 from the AppExchange.

If you are running version 18 or earlier, you must upgrade immediately. Adobe support has ended for these versions.

• We will begin turning off versions 14 and below starting December 9, 2019. 
• Versions 17 and below will be turned off on Feburary 3, 2020.

Important

Please review the release notes and test in a Sandbox org before upgrading your Production instance. This is an important step if you have developed a custom solution. Object definitions may have changed and you may be required to update your customization.

Please keep the API version of Lightning Locker at 46 when Salesforce Winter ’20 is released. Please see the release notes from Salesforce on Lightning Locker version.

Refer to the release notes for additional information on the newest features in Adobe Sign for Salesforce.

Stay updated

Adobe recommends, as best practice, that customers always upgrade to the latest version of Adobe Sign for Salesforce, as this version provides the latest security patches and “older” versions have an “End of Support” date. You may also be missing out on the latest solution to automate and accelerate your business.

We’ve added support for Salesforce process builder, Community Cloud, email integration, Salesforce CPQ support, and full Lightning support including drag and drop ease on any device. See complete list of all the latest features and solutions here.

Planned “End of Life” for old versions of Adobe Acrobat Reader for digital signatures in January 2020

Adobe Sign customers applying digital signatures with the Download and Sign With Acrobat option using Adobe Acrobat Reader on a desktop computer must upgrade to a recent version of the software.

ACTION REQUIRED

Please upgrade old versions of Acrobat Reader to one of the following:

• Adobe Acrobat Pro or Acrobat Standard
• Acrobat Reader
• Acrobat Reader XI version 11.0.7 or later.

Please upgrade before the end of December 2019.

Impact

Customers currently using the Download and Sign With Acrobat option with older versions of Acrobat Reader will need to upgrade to successfully apply a digital signature after December 2019. After that date, when using older versions, the following message will be shown but users will not be able to apply their digital signature:

More details

This change derives from the removal of the “Reader Extension” enablement from PDF files generated by Adobe Sign starting from January 2020. Reader Extension was required by old releases of Adobe Acrobat Reader prior to version 11.0.7 to enable digital signatures. This feature is not technically feasible from some new cloud platforms hosting Adobe Sign.

In addition, the new requirement has been introduced to minimize security threats associated with using insecure and unsupported versions of Adobe Acrobat Reader to apply digital signatures.

Email templates and the post-signing confirmation page are changing with the November release

The November release includes new email templates for the Please Sign and Signed and Filed base templates.

All customers that are using the base templates (not a Custom Email Template) will inherit the new templates by default.

ACTION REQUIRED

No action is required and you will inherit the new templates seamlessly.

Updates to Mobile Signing Experience

In our November 2019 launch, improvements will be made to the Adobe Sign recipient experience which include:

• Responsive design for signer emails
• Signer experience in a mobile web browser

Key changes on emails include:

• Removal of agreement thumbnail 
• Subject line changes on Request emails, for example:
  • From: “Please <participant action> <agreement name>” to “<participant action type> requested on <agreement Name>
    • eg. “Please Sign <agreement Name> to “Signature requested on <agreement Name>"
    • eg. “Please Approve <agreement name> to “Approval requested on <agreement name>"
• Subject line changes on Signer confirmation emails, for example:
  • From "<Agreement Name>between <Company Name> and <Signer Full Name>) is Signed and Filed!", to "You Signed <agreement Name>"

The signer experience updates include: re-designed mobile responsive signer emails, and changes to streamline the agreement filling and signing experience. Key changes include:

• Agreement name pop up on viewing of agreement
• Sender message available in ‘More Options’ (hamburger) menu
• Navigation bar for guided field navigation and required field countdown
• Improved smooth zoom for gestures
• Double-tap gesture to zoom
• Removal of thumbnail, ‘Reminder’ and “Send another’ links from the post sign confirmation screen

New SSL Certificate Available -
Going into effect October 5th, 2019

Adobe Sign is releasing a new SSL Certificate on October 5^th, 2019.
There is no change to the public key, underlying cryptographic protocols or scheme.

The new certificate is available  by downloading it from Adobe Sign System Requirements.

ACTION REQUIRED

Use of the public key
If you have custom built integrations with Adobe 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’re pinning  the certificate itself or using other methods, you can find the new Adobe Sign certificate in the Adobe Sign System Requirements.

The new SSL certificate will become active on October 5^th 2019.

Important changes to IP address ranges

If your existing network or firewall configuration explicitly allows the IP addresses for Adobe Sign, update the network configuration settings to include the new IP addresses to ensure continued access to the service.

Most of the existing IP addresses will continue to be in service and must not be deleted or removed from your network configuration.

See a complete list of IP address ranges in system requirements ›

ACTION REQUIRED

If you use the Adobe Sign for Salesforce integration, admins must explicitly allow the additional IP address ranges in their Salesforce.com account (including Sites).

ADD: 51.105.221.160/27

If you explicitly list the IP ranges for outbound email relays:

ADD: 51.105.221.64/30

New Release: Adobe Sign November 2019

The Adobe Sign November 2019 product release is scheduled for early November.

This product release includes new features and feature enhancements for administrators and end users.

No down time is expected with this release. 

End of Support for Sign Mobile OS Versions

End of Support for Sign Mobile OS Versions

To take advantage of the latest released features in the Sign mobile applications.

• The Adobe Sign iOS mobile app will require iOS 11 and up
• The Adobe Sign Android mobile app will require Android 5 and up

Adobe Sign mobile apps support the most recent released versions of iOS and Android. We will continue to support the following moving forward:

• Latest version and up to one version back for iOS
• Latest version and up to four versions back for Android

ACTION REQUIRED

Upgrade to the latest supported mobile OS version to get access to the latest features.

Adobe Sign mobile apps on older operating systems will continue to work but will not be updated with most recently released features.

Alert messages occurring in automated workflows after June 20th 2019

Starting June 20 2019, automated workflows using document templates with incompatible scopes will display an alert message for both senders (in the classic experience) and admins. These alert messages will not affect the ability to use the automated workflows, however steps should be taken to update the incompatible document templates.

End users will see the alert “This workflow contains documents that are out of scope for users in your account.” Administrators will see the alert “This document template has an inconsistent access scope for this Workflow.”

Full details on this and how to resolve the alert messages are available.

Custom Workflow Error Messaging

Customers that use the Custom Workflow Designer may be seeing errors that indicate document/authority issues.  

Admins can request their success manager to suppress these error messages while the workflows are being corrected.

New Release: Adobe Sign August 2019

The Adobe Sign August 2019 product release was completed August 14th with no down time to the service.

This product release includes added functionality to the new manage page (support for web forms and mega sign transactions) and infrastructure enhancements to further improve platform stability.

New Release: Adobe Sign May 2019

The Adobe Sign May 2019 product released May 21st.

This product release includes new features and feature enhancements for administrators and end users. 

No downtime for the service was experienced during this release.

Adobe Sign for "Workplace by Facebook”

Adobe Sign for “Workplace by Facebook” is expected to release in early 2019. This integration allows users to send documents for signature, check the status of all of their agreements, and get Sign notifications inside Workplace Chat.

For more information:

• Adobe Sign in Workplace by Facebook marketplace: https://www.facebook.com/workplace/integration?app_id=178288246261553
• User Guide: https://helpx.adobe.com/sign/help/adobesign_fbw_user_guide.html
• Installation Guide: https://helpx.adobe.com/sign/help/adobesign_fbw_install.html

New release: Adobe Sign for Salesforce v21

Adobe Sign for Salesforce v21 is now available. This release includes new features for administrators and users, including: 

• Set repeatable signing flows - Revamped Agreement Template makes is easy to create and maintain your signing workflows via Adobe’s Agreement Templates
• Community Cloud - Get documents signed with Adobe Sign on any Salesforce Portal (customer, partner, employee, citizen).  Users initiate and manage their agreements right from your portal
• Salesforce CPQ Connector - Updated CPQ connector to enable payments collection when signing the document and adding form fields
• Government Issued ID - Require signers to verify their ID with a government issued ID

The update is available on Adobe Sign’s Salesforce AppExchange listing. 

New (2019) W-4 template available

The new IRS W-4 (2019) form has been added to the Adobe Sign library, entitled W-4 2019 (Employee's Withholding Allowance Certificate)

ACTION REQUIRED

The new W-4 form template has a new libraryDocumentId. If you use the existing template’s libraryDocumentId in your applications, you will need to update it.

The 2018 version is to be removed from the system in May, 2019.

Any application/API using the legacy (ver 2018) form must be updated before May 1^st to ensure no disruption to successful service.

To find the libraryDocumentId in an API-enabled account:

1    Log in as an Account Admin

2    Click on the Account tab > Adobe Sign API > API Information > click the link: REST API Methods Documentation

3    In the GET /libraryDocuments section, click the OAUTH ACCESS-TOKEN button 

a. Enable the library_read:self scope

4    Click the Try it out! button

5. In the Response Body, locate the new W-4 2019 (Employee's Withholding Allowance Certificate) form template (not ver. 2018) to see the libraryDocumentId value. 

Customers that prefer to manage the tax form within their account library can download a fully tagged PDF here.

If you need more information, please contact your Customer Success Manager.

Immutable Audit Reports have been rolled out to enterprise and business accounts

The December release introduced the new immutable audit report to Adobe Sign at the team, individual, and free levels of service.

As of the February 19th patch release, the enterprise and business tiers of service have adopted this new format.

For more details on the new immutable audit reports, please refer to this article.

New (2019) W-9 template available

The new IRS W-9 form has been added to the Adobe Sign library entitled W-9 (Request for Taxpayer Identification Number) ver. 10/18

ACTION REQUIRED

The new W-9 form template has a new libraryDocumentId. If you use the existing template’s libraryDocumentId in your applications, you will need to update it.

The 2017 version is to be removed from the system in April, 2019.

Any application/API using the legacy (ver 11/17) form must be updated before April 1^st to ensure no disruption to successful service.

To find the libraryDocumentId in an API-enabled account:

1    Log in as an Account Admin

2    Click on the Account tab > Adobe Sign API > API Information > click the link: REST API Methods Documentation

3    In the GET /libraryDocuments section, click the OAUTH ACCESS-TOKEN button 

a. Enable the library_read:self scope

4    Click the Try it out! button

5. In the Response Body, locate the new W-9 (Request for Taxpayer Identification Number) ver. 10/18 form template (not ver. 11/17) to see the libraryDocumentId value. 

If you need more information, please contact your Customer Success Manager.

Customers that prefer to manage the tax form within their account library can download a fully tagged PDF here.

Security Notice for the Adobe Sign for Salesforce integration

Versions impacted: All versions prior to 20.9

Adobe Sign for Salesforce customers using a Salesforce Site must take action. The Salesforce security team recently reported a vulnerability. There has been no reported impact to Adobe Sign customers, but action is required.

You can find full details of the required action on this page, as well as information on how to determine if you are using a Salesforce Site.

Salesforce instance update

Salesforce is performing infrastructure upgrades which may result in the name of your Salesforce instance changing. If this occurs, you will need to refresh your auto update setup.   To do this, go the Adobe Sign Admin page and select Enable Automatic Status Updates.

How can I get more information?

For more information, please contact Support through the Adobe Sign application. Your Support options are presented by first signing in to Adobe Sign (https://secure.echosign.com/public/login) and then selecting the “?” up in the top right-hand corner. Alternatively, contact your customer success manager.

Support for the Adobe Sign for Salesforce integration v18.x and lower ends March 1, 2019.

Product updates, security updates and technical support for Adobe Sign for Salesforce v18 will end on March 1, 2019.

ACTION REQUIRED

Upgrade to the latest version of our integration with Salesforce to continue to receive the latest features, security updates and technical support.

Adobe Sign for Salesforce integration v18.x Upgrade

All customers are recommended to upgrade to the latest version of Adobe Sign for Salesforce before March 1 2019.

Re-authenticating your account for automatic status updates from Adobe Sign will no longer work after March 2019 for v18 and lower. 

If you are running version 18 or earlier, you MUST upgrade in order to continue to receive support.

Adobe recommends, as best practice, that customers always upgrade to the latest version of Adobe Sign for Salesforce, as this version provides the latest security patches and “older” versions have an “End of Support” date. 

Fill & Sign is the default to sign anything you’ve been sent

In December 2018, the Fill & Sign interface was enabled as the default way to sign any document you’ve been sent from outside the Adobe Sign service.

Fill & Sign provides the flexibility of a free-form filling and signing experience while providing the trust and security you expect from Adobe Sign electronic signatures.

Our Classic Only I Sign functionality continues to be available via a switch for enterprise customers, but will be eventually discontinued in favor of the simplified Fill & Sign experience.

Adobe Sign for Salesforce v20.11 update
(incremental patch)

A new patch for Adobe Sign for Salesforce is available on AppExchange. 

This patch brings several improvements and fixes for Edge and Internet Explorer browsers.

The full list can be found in the release notes.

New Release: Adobe Sign December 2018 product release

The December 2018 product update released on schedule with several feature improvments.

Reveiw the updated content in the release notes.

Integration: Support for the Adobe Sign for Salesforce integration v16 and v17 has ended as of November 15, 2018

Product updates, security updates and technical support for Adobe Sign for Salesforce v16 and v17 has ended as of November 15, 2018. 

ACTION REQUIRED

Upgrade to the latest version of our integration with Salesforce to continue to receive the latest features, security updates and technical support.

Integration: Support ended for Adobe Sign for Dynamics v5

Support has ended for Adobe Sign for Dynamics v5.  Adobe Sign for Dynamics 365 CRM  v7 was released in June.

Customers using Dynamics onPrem and Online 365, who have not yet done so, should update to the latest version which is available for download on Adobe Sign’s Microsoft AppSource listing.