Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > TLS compatibility with Orion Platform products

TLS compatibility with Orion Platform products

Created by Alexandra.Nerpasova, last modified by Steve.Hawkins on Nov 12, 2018

Views: 7,389 Votes: 16 Revisions: 69

Updated November 12, 2018


This article details the versions of TLS supported by SolarWinds products, including which products are able to run on TLS 1.2 only. 


  • Orion Platform products
  • Other SolarWinds product, such as NTM


SolarWinds products running on the Orion Platform use TLS 1.0, 1.1, or 1.2, depending on the product.


Orion Platform 2016.2 added support for TLS 1.1 and 1.2, but not all products that consume Orion Platform 2016.2 support TLS 1.1 or 1.2. 

Starting with Orion Platform 2017.1, some Orion Platform products support running solely on TLS 1.2, with versions TLS 1.1 and TLS 1.0 disabled. Use the table below to see which products support running on only TLS 1.2 and which products also need TLS 1.1 enabled to work properly.


No version of any Orion Platform product prior to Orion Platform 2017.1 will run on TLS 1.2 only. Some legacy tools such as the Report Writer, Syslog Viewer, and Trap Viewer may require TLS 1.0.

Temporarily enable TLS 1.1 to install additional polling engines or additional web servers (Orion Platform 2017.1 and later)

To install an additional polling engine or additional web server for any product that runs on TLS 1.2 only, temporarily enable TLS 1.1 to complete the installation:

  1. Enable TLS 1.1.
  2. Install the additional poller or additional web server.
  3. After completing the installation, disable TLS 1.1 and continue using the product with only TLS 1.2 enabled.

TLS compatibility

Use this table to see which products support running on only TLS 1.2 and which products also need TLS 1.1 enabled to work properly.


TLS 1.0  from version TLS 1.1 
from version
TLS 1.2 from version

Works with only TLS 1.2 enabled?

Earliest version that supports TLS 1.2 only Notes
APM    1.0* 1.0 Yes 1.0 *TLS 1.1 is supported but not recommended.


  11.0 11.0


EOC   2.0 2.0 Yes 2.0  
IPAM   4.5 4.5 Yes 4.7  
ipMonitor     10.8.3 Yes 10.8.3  
NCM       Yes 7.8  
NPM   12.0.1 12.0.1 Yes 12.3  
NTA 4.2.1 No 4.4 Yes 4.4 4.2.3 and older requires TLS 1.0 to be enabled.
NTM       No – Also needs TLS 1.1 enabled N/A  
Patch Manager     2.1.5 Yes 2.1.5  
SAM   6.3 6.3 Yes 6.6.1 SAM application polling is able to fall back to TLS 1.1 or  TLS 1.0 for HTTPS website polling and SSL Certificate monitoring if the later version is not working properly in your environment.
SRM       Yes 6.4

When negotiating the connections to arrays, the protocols are used in descending order: TLS 1.2, TLS 1.1, TLS 1.0 and SSL 3.0. The protocol used depends on your arrays, the versions of those arrays and what they support.

SRM with SRM Profiler integration does not support TLS 1.1 or TLS 1.2. 

Toolset       No - Also needs TLS 1.0 or 1.1 N/A  
UDT   3.3 3.3 Yes 3.3  
VMAN     8.0 Yes 8.2.1  
VNQM   4.2.2 4.4 Yes 4.5  
WPM   2.2.1 2.2.2 Yes 2.2.2 For monitored websites, you can enable TLS 1.1 and 1.2 for the WPM player.



This content is maintained by the Technical Content group.

To suggest changes or provide comments, click the Leave feedback link to the right or send an email to

Last modified