- Welcome to Adobe Acrobat Sign for Government
- First steps for new accounts
- Claiming an email domains
- Connecting Okta to a federated identity solution
- Manually create/edit users in Okta
- First steps for new accounts
- Configure Acrobat Sign
- Configuration Overview
- System requirements
- Branding
- User access to features
- User experience within the application
- Recipient experience when interacting with agreements
- Transaction security
- Compliance information
- Configuration Overview
- Administrator processes
- Admin guide overview
- Users
- Groups
- Templates
- Custom workflow designer
- GDPR deletion processes
- Sandbox
- User environment and processes
- Support resources
- Transaction limits
- Page layouts
- Configure your profile
- Send agreements
- Compose an agreement to send for signature
- Recipient signing order
- Written signatures
- Send an agreement to yourself only
- Send in Bulk
- Sending from a template on the Manage page
- Sign agreements
- Fill and Sign a document
- Self Signing
- Signing a document from an email link
- Sign a document from the Manage page
- Compose an agreement to send for signature
- Custom workflow designer
- Manage agreements
- Search for agreements
- View Agreements
- Activity history and Audit Report
- Add a note to an agreement
- Set a reminder
- Cancel a reminder
- Add an expiration date
- Modify/Delete an expiration date
- Modify the files of a sent agreement
- Replace the current recipient
- Upload a signed agreement
- Share an individual agreement
- Download an agreement
- Download the individual files of an agreement
- Download the audit report
- Download the signer identity report
- Download the field data from an agreement
- Cancel an agreement
- Hide an agreement from view
- Reporting
- Create a report with classic reporting
- Report charts and data exports
- Data Exports
- Report Charts
- API
Adobe Acrobat Sign for Government System Requirements
The following system requirements apply to the Adobe Acrobat Sign for Government service.
Supported Operating Systems
- Microsoft Windows 10 or newer
- MacOS 11 (Big Sur) or newer
Supported Browsers
The latest versions of:
- Safari
- Chrome
- Edge
- Firefox
The Microsoft Edge browser does not natively support 256-bit AES encryption of PDF files. If you are using the Edge browser, please ensure you are running the latest version of Adobe Reader.
Supported document formats
- 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)
Software required to view a signed document
- 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
Software required to sign a document
- Electronic signautres: Applied via any supported browser
- Cloud-based digital signatures: Applied via any supported browser
- Digital signatures via “Download and Sign with Acrobat”: Must use Adobe Acrobat or Adobe Acrobat Reader XI v11.0.7 or later
Domains to explicitly allow
Users with restrictive email security will need to explicitly permit inbound email from adobesign@adobesign.us to avoid filtering.
The out-bound email IP ranges for Adobe Acrobat Sign can be found here >
Accounts with restrictive network security will need to explicitly permit Adobe required domain names. The following domains must be allowed to ensure basic functionality:
- *.adobesign.us
- *.adobesigncdn.us
If you explicitly allow IP addresses on your network, please add the below IP range to your firewall:
North America:
- 52.245.243.96/28
IP ranges for outbound mail relays
If your organization explicitly lists IP addresses to control connection to your inbound mail servers, add the following IP address to your allowed list of IP ranges:
- 52.245.243.112/28
SSL/TLS Requirements
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. Connections to Acrobat Sign require use of TLS 1.2 and support for at least one of the cipher suites below. These requirements apply both to inbound traffic to Acrobat Sign servers (browsers, API) and outbound traffic from Acrobat Sign servers to customer servers (API callbacks used for retrieving agreement source documents, returning status, and webhooks).
For browsers: as long as you adhere to the OS/Browser requirements, you should have no browser-related issues. All these OS/browsers are fully compliant with our TLS requirements.
For applications using the Acrobat Sign API, these frameworks support TLS 1.2:
- Java: use Java11 or later
- .NET: use .NET 4.6 or later
- OpenSSL: use OpenSSL 1.0.1 or later
For servers used to received callbacks or webhook requests from Acrobat Sign:
- Support TLS 1.2 and at least one of the cipher suites listed below
- Have a valid TLS certificate, and include all intermediate certificates.
Customers who wish to test that their server is compliant can use a variety of free or commercial tools, including the Qualys SSLLabs Server Test, to ensure that their server accepts TLSv1.2, supports at least one of the cipher suites below and has a valid certificate.
TLS Cipher Suites Allowed:
- ECDHE-ECDSA-AES256-GCM-SHA384
- ECDHE-RSA-AES256-GCM-SHA384