This topic explains Brightcove’s support for TLS and HTTPS for secure delivery of online media.
Transport Layer Security (TLS) encrypts and protects data transferred over the Internet. Since data delivered over the web can be delivered with or without encryption, it is the client (e.g., browser) that notifies the server that the data needs to be encrypted. This is usually done by using the HTTPS protocol in the URL instead of HTTP.
Video Cloud supports TLS for all media delivery under the following conditions
– If you are using the Brightcove CDN, you can contact Brightcove support to have your account configured for HTTPS + HTTP data delivery or for HTTPS-only delivery.
– If you are using another CDN (also known as a BYO CDN), you can request these options from your CDN.
Whether TLS is required depends primarily on whether the site or page that is serving the video is loaded over HTTPS. If TLS is required, then the video, video assets, player, and API requests must also be requested over HTTPS. Otherwise, the viewer’s browser will display a warning or will not load.
## Changes to TLS Support
Brightcove is changing its support for TLS versions as detailed below, in accordance with recommendations from internet security experts.
**What are the changes?**
After June 30, 2018, Video Cloud will no longer support TLS versions 1.0 or 1.1. While we will not be immediately stopping support for 1.0 or 1.1, we will no longer support these protocols and recommend that you migrate as soon as possible.
**Why is Brightcove deprecating older TLS versions?**
The security of customer data is Brightcove’s top priority. These changes are being deployed across the industry, and many technology partners have already taken steps to disable older versions of TLS. These changes are necessary to maintain best practices and ensure that the latest compliance requirements of the PCI Security Standards Council are met.
**When will Brightcove stop supporting older TLS?**
At this time, we do not plan to disable TLS 1.0 or 1.1 on all endpoints. However, many upstream providers have plans to discontinue support, and when that support ends, we will no longer be able to support those protocols. We will provide information on our System Status page when such plans are advanced by our service.
**How do I know if I am ready for this change?**
Since TLS 1.0 / 1.1 are deprecated, you will need to use TLS 1.2 encryption protocol (or later) to connect to the Video Cloud platform. We will try to minimize the impact, but there are two risks
– 1. You will need to ensure that all connections to the Video Cloud API (such as calls to the CMS API from Python scripts) are made from platforms that support TLS 1.2 or later. This means that automated processes will need to be hosted from compatible browsers.
– 2. Users may be affected if they are using unsupported browsers, have disabled the relevant encryption protocols, or are using unsupported devices.
We expect that only a small percentage of users will be affected, and only on older devices and browsers. For a sample of unsupported clients and devices, please see below.
**Unsupported platforms (players/SDKs)**
HTTP connections are not affected by the change. The following is a list of older user agents that do not support HTTPS connections using TLS 1.2.
**OS / browser combinations**
– Windows 7 / Chrome 29 (or earlier Chrome versions)
– Windows 7 / Firefox 10.10.12, Firefox 17.0.7, Firefox 24.2.0, Firefox 22, Firefox 24
– Windows 8 / Firefox 26
– Windows XP / IE 6
– Windows Vista / IE 7
– Windows Phone 8.0 / IE 10
– Windows 7 / Opera 12.15, Opera 15, Opera 16
– OS X 10.6.8 / Safari 5.1.9
– OS X 10.8.4 / Safari 6.0.4
– Android 4.3 and earlier
**Other unsupported platforms and devices**
You will need to validate integration on platforms and devices where we do not provide a player or SDK, or where you have created a custom integration with our API. The following list is not exhaustive, but includes many platforms and OEM devices that do not support TLS 1.2.
**Software libraries and runtime environments**
– Java 6u45
– Java 7u25
– OpenSSL 0.9.8y
**Smart TVs / OEM devices**
– 2015 Panasonic CS650 TV
– 2014 Sharp TV – UD20, U20, US20, W20, W25, R30, XL20, G20
– PlayStation 3
– PlayStation Vita
## Enabling TLS 1.2
In some cases, TLS 1.2 may be supported but disabled. To enable the TLS 1.2 protocol in your Windows web browser, please refer to the following.
**Microsoft Internet Explorer**
– 1. Open Internet Explorer
– 2. From the menu bar, click on [Tools] > [Internet Options] > [Advanced] tab
– 3. Internet Explorer settings
– 4. Internet Explorer settings
– 5. Scroll down to the Security category and manually check the box next to the option Use TLS 1.2
– 6. Click OK
– 7. Close the browser and restart Internet Explorer
**Google Chrome**
– 1. Open Google Chrome
– 2. Click Alt F and select Settings
– 3. Scroll down and select Show advanced settings
– 4. Scroll down to the [Network] section and click on [Change Proxy Settings
– 5. Select the [Advanced] tab
– 6. Scroll down to the [Security] category and manually check the option boxes for [Use TLS 1.1] and [Use TLS 1.2
– 7. Click OK
– 8. Close the browser and restart Google Chrome
**Mozilla Firefox**
– 1. Open Firefox
– 2. Type “about:config” into the address bar and press Enter
– 3. Type “tls” into the “Search” field. Find the entry for “security.tls.version.max” and double-click on it
– 4. To force the TLS 1.2 protocol, set the integer value to 3
– 5. Click OK
– 6. Close the browser and restart Mozilla Firefox
**Opera**
– 1. Open Opera
– 2. Click Ctrl + F12
– 3. Scroll down to the [Network] section and click [Change proxy settings
– 4. Select the [Advanced] tab
– 5. Scroll down to the [Security category] and manually check the option boxes for [Use TLS 1.1] and [Use TLS 1.2
– 6. Click OK
– 7. Close the browser and restart Opera
[Reference URL](https://studio.support.brightcove.com/general/content-protection/tls-media-player-and-api-urls.html “Reference URL”)
\[Modified on 06/06/2018\] The content has been modified due to changes in the content.
