Browsers are expected to start requiring a minimum version of TLS 1.2 when using HTTPS. To prepare for this change, we recommend you ensure your Sisense server is configured to enforce use of TLS 1.2.
If you are a Sisense Managed Cloud customer, no action is required by you: Sisense will handle this configuration for you.
If you are self-hosted, please follow these instructions for configuring support for TLS 1.2 on your Sisense server.
Windows Versions up til 7.1.3
Support for TLS 1.2 should be configured at the operating system level. See details in this Microsoft article.
Windows Versions 7.2.x and 7.3
No action is required, as these versions already support using TLS1.2. The cipher is determined by the browser or the client, and cannot be enforced by Sisense server.
Windows Versions 7.4.x - 8.1.2
These versions support using TLS1.2, but this transport layer is not enforced by default. Update the setting available in the Configuration Manager, Web Server section, “Enforce TLS V1.2” to configure the system to enforce it.
Windows Version 8.1.3 and above
The version supports using TLS v1.2 by default. Instructions for configuring the cipher list are available here: https://www.openssl.org/docs/man1.1.0/man1/ciphers.html
All Linux versions starting from Linux 7.4.3 use TLS 1.2 by default, and no action is required.
Any version using a Load Balancer for SSL termination
If the deployment has a Load Balancer used for SSL termination, you must configure the Load Balancer to enforce the TLS 1.2 version. Communication between the Load Balancer and the Sisense server is over HTTP, and no additional configuration is required on the Sisense server.
- Modernizing Transport Security (Google Security Blog)
- Removing Old Versions of TLS (Mozilla Security Blog)
- Modernizing TLS connections in Microsoft Edge and Internet Explorer 11 (Microsoft Windows Blog)
- Deprecation of Legacy TLS 1.0 and 1.1 Versions (Apple’s Secure Transports team guest post at WebKit))
- Chrome Update Schedule
- Firefox Release Schedule
If you experience any issues with these instructions, please open a support ticket.
Ahuva Hazan-Fuchs | Product Director