The following system requirements apply to Adobe Sign (formerly Adobe Document Cloud eSign services or Adobe EchoSign).
- Microsoft Windows 10 using Microsoft Edge, Internet Explorer 11, Firefox, or Chrome
- Microsoft Windows 8 using Internet Explorer 11 or later, Firefox, or Chrome
- Mac OS X v10.9 or later using Safari 7 or later, Firefox, or Chrome
The Microsoft Edge browser does not natively support 265-bit AES encryption of PDF files.
If you are using the Edge browser, please ensure you are running the latest version of Adobe Reader
- Adobe PDF (.pdf)
- Microsoft Word (.doc and .docx)
- Microsoft Excel (.xls and .xlsx)
- Microsoft PowerPoint (.ppt and .pptx)
- Text (.txt)
- Rich Text (.rtf)
- Graphics (.tif, .jpg, .jpeg, .gif, .bmp, and .png)
- Web (.htm or .html)
TLS 1.2 Requirement
Transport Layer Security (TLS) is the most widely deployed security protocol used today for Web browsers and other applications that require data to be securely exchanged over a network.
You passively use it whenever you open a browser, and as long as you adhere to the OS/Browser requirements, you should have no browser related issues.
Below is a list of other frameworks, defining their minimum version levels to be TLS 1.2 compliant:
- Java: use Java 8 or later. Java 7 may be used but requires TLSv1.2 to be explicitly enabled by the application
- .NET: use .NET 4.6 or later.
- .NET 4.5 may be used but requires TLSv1.2 to be explicitly enabled by the application.
- .NET depends on TLS 1.2 support by the Windows OS it runs on
- For applications using OpenSSL: use OpenSSL 1.01 or later
- Adobe Reader 9.0 or later for documents secured with AES 128-bit encryption or lower
- Adobe Reader 10 or later for documents secured with AES 256-bit encryption
If you explicitly whitelist IP addresses on your network, please add the below IP ranges to your firewall:
If your organization whitelists IP addresses to control connection to your inbound mail servers, add the following IP addresses to your whitelist:
Adobe Sign uses the following SSL Certificates. If you have custom built integrations with Adobe Sign using either the SOAP or REST APIs, and if any of these integrations requires “pinning” or whitelisting the actual certificates, you can find the new Adobe Sign and CA certificates below.