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 Cascade require the use of TLS 1.2 and support for at least one of the cipher suites below. These requirements apply both to inbound traffic to Cascade servers (browsers, API) and outbound traffic from Cascade 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 Cascade API, these frameworks support TLS 1.2:
- Java: use Java 8 or later
- .NET: use .NET 4.6 or later
- OpenSSL: use OpenSSL 1.0.1 or later
For servers used to receive callbacks or webhook requests from Cascade:
- 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 Supported:
| 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 |