Doing the following registry changes will enforce it to use TLS 1.2 But by default, it would always initiate the communication in TLS 1.0. Once you have installed the above windows patches in the SSRS server, it is now capable of initating a communication over TLS 1.2. If it’s a production environment you would have certificate already installed in your environment.īut in both the scenarios you need to make sure that certificates are installed in If you are testing this in your lab environment then you can create a self-signed certificate and use it. If you notice the below screenshot, you would see that we have only one HTTPS URL, there is no HTTP URL. You need to do that for both Report Server and Report Manager URLs. In your Reporting Services configuration manager, you need to explicitly disable and need to keep only enabled. If you have already installed this patch, you will end-up seeing the below message when you run the installer one more time. The download link is present in the below KB article link. You can find these updates in the below article.Īfter this, based on the operating system that you are on, you need to install the. Reporting Services Related configuration (SERVER 2)īefore we start configuring the changes, I would like to tell you that a couple of months back this wasn’t a supported scenario but right now Reporting Services can communicate with SQL Server using TLS 1.2īefore you install the patch, you need to make sure that the SQL Server TLS 1.2 support updates are already installed.

It could be easily explained with following diagram. You may even need to consider about the Report Data sources communication as well if the hosted SQL instances of the Report Server database and Report databases are different. Let us consider a scenario, let us say if you have custom application which has integrated reports from the Reporting Services then in that case you need to make sure that the TLS 1.2 communication is happening between your custom application and Reporting Services as well as between Reporting Services and Report Server databases. You might be thinking about using TLS 1.2 as a protocol to do all the communication. If you are using any custom application which is integrated with any payment gateway you might be thinking of using a secure protocol while doing the communication between them.

Test tls 1.2 support in net framework