Orion and TLS 1.2?

Are you talking about the HTTPS monitor or disabling TLS 1.0 and 1.1 on the Orion website? .NET 4.0 Framework is the limiting factor for TLS. The latest version of SAM 6.2.3 is built on .NET 4.5x and now supports TLS 1.2.

I am talking about disabling TLS 1.0 and 1.1 on my Orion website.

There is a free tool that I use called " IIS Crypto" to easily disable ciphers and protocols on any IIS web server. Google it, download it, test disabling the ciphers that you don't want. A reboot may be required after you make changes.

Thanks; however, my problem isn't disabling them as I know how to do that.  The issue is when I tried disabling them it broke Orion which indicates to me that Orion may be still relying on TLS 1.0 and/or 1.1.

What I am looking for is confirmation on if Orion Web Server supports running on just TLS 1.2 and if so what specific considerations or configurations may need to be made.

Orion does not yet at this time support TLS 1.2.  SAM 6.3 (currently in beta) does however support TLS 1.2.

Thanks aLTeReGo​!  So is that just a SAM thing or is that going to be supported throughout the entire Orion suite soon?  We not only have SAM but also NCM and IPAM.

In theory, after upgrading to SAM 6.3 and NPM 12 the other modules should inherit the necessary changes required to support TLS 1.2, but since I have not tested each module myself I cannot confirm that at this time. The reason why TLS is not supported is that Orion is written using the .NET Framework 4.0, which does not support TLS 1.2. We are in the process now of moving to .NET 4.5 which does support TLS 1.2.

Awesome, thanks for this info.  Once I have upgraded to those new versions I will be happy to test.

I was able make working monitoring with SSL and HTTPS monitor from SAM 6.2.x, when all protocol except TLS 1.2 were disabled.

prerequisite is to have on Orion server .NET framework 4.5.x installed.

For other details see this article HTTPS Monitor and SSL Certificate Expiration Date Monitor reports down status when TLS 1.0 disabled on monitored IIS ser…

I am having this problem where we disabled TLS 1.0 on a few servers and as soon as we did my HTTPS and Cert Expiry Monitors against those servers failed immediately.   Can I just go ahead and upgrade .NET to 4.5.2 on my SW server and those monitors will work again or do I need to wait until SAM can be upgraded to 6.3 also ?  If you can just upgrade .NET,  any cautionary tales out there where that induced other problems ?  and if it did cause new problems  can you just uninstall .NET 4.5 and re-install .NET 4.0 ?  Thanks in advance