Forum Discussion
Solved
Azure Web App / Https calls to SQL Server Reporting Services
Hi all. I'm working on troubleshooting an Azure Web App that is making an https call to an SSRS server located on an Azure VM. This web app works when making an http call to the SSRS server but never...
- This problem has been fixed and Wireshark helped identify what the problem was. After installing Wireshark and then having the Azure web app make a call to the SSRS web site, Wireshark showed the web app was making the call using using TLS 1.0. For security reasons, TLS1.0 and TLS1.1 was disabled on the SSRS server. So when the web app attempted to set up a TLS session using TLS1.0, the SSRS server denied it. To fix things, the Azure web app had to have a line of code added to force the TLS1.2 connection. In this case it was: ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
In addition, the SSRS configuration has to be set up using an SSL certificate from a trusted Certificate Authority. I tried using a cert issued from our internal CA and it didn't work. I ended up using a cert from a well known CA.
So there you have it. I hope this helps someone in the future.
This problem has been fixed and Wireshark helped identify what the problem was. After installing Wireshark and then having the Azure web app make a call to the SSRS web site, Wireshark showed the web app was making the call using using TLS 1.0. For security reasons, TLS1.0 and TLS1.1 was disabled on the SSRS server. So when the web app attempted to set up a TLS session using TLS1.0, the SSRS server denied it. To fix things, the Azure web app had to have a line of code added to force the TLS1.2 connection. In this case it was: ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
In addition, the SSRS configuration has to be set up using an SSL certificate from a trusted Certificate Authority. I tried using a cert issued from our internal CA and it didn't work. I ended up using a cert from a well known CA.
So there you have it. I hope this helps someone in the future.
In addition, the SSRS configuration has to be set up using an SSL certificate from a trusted Certificate Authority. I tried using a cert issued from our internal CA and it didn't work. I ended up using a cert from a well known CA.
So there you have it. I hope this helps someone in the future.