Support for TLS 1.2

PCI compliance is driving this request for us to use TLS 1.2.

We had opened a case with you regarding this support. # 1019445

Thank you.

Find more posts tagged with

tls1.2

Status: None

Solarwinds, get with the program. I would like to monitor Meraki devices but I don't want to expose our environment to do so.

I too, would like to be able to monitor my Meraki devices with the API. Please dedicate some time for your developers to address this issue.

TLS1.0 only! what a joke, Solarwinds, goan and fix this. I have customers laughing at me when I explain this

TLS 1.2 is supported for Orion Platform 2017 and higher. To enable TLS 1.2, you need to enable in the registry to use TLS 1.2:

Restart is required for change to take effect. Run the following in PowerShell, then reboot system: (IIS Website already configured for STIG) IIS 8.5 web server session IDs must be sent to the client using TLS.

- 1. New-Item 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server' -Force | New-ItemProperty -Name Enabled -Value 1 -Force | Out-Null
  2. Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server" -Name "DisabledByDefault" -value 0
- Note: If you plan to use MS SQL with SSL enabled, please also apply TLS 1.2 Server to the MS SQL Server, and Client Registry settings below to the Solarwinds Server.

- New-Item 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client' -Force | New-ItemProperty -Name Enabled -Value 1 -Force | Out-Null
- Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client" -Name "DisabledByDefault" -value 0
- You will also want to apply TLS 1.2 Client your client endpoint systems.
  - Microsoft Reference: https://docs.microsoft.com/en-us/windows-server/security/tls/tls-registry-settings#tls-12