Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Kiwi Syslog Server > Kiwi Sys - Knowledgebase Articles > Enable TLS 1.2 in Kiwi Syslog Server 9.6.5

Enable TLS 1.2 in Kiwi Syslog Server 9.6.5

Table of contents

Updated June 19, 2018

Overview

As of version 9.6.5, Kiwi Syslog Server users can now connect via TLS 1.2 to comply with new TLS standards. This article details the necessary steps to enable TLS 1.2 in Kiwi Syslog Server 9.6.5

Environment

  • Kiwi Syslog Server 9.6.5

Steps

Note: Kiwi Syslog Server 9.6.3 and earlier DO NOT support TLS 1.2.

To enable TLS 1.2 protocols in your KSS environment, complete the following steps:

  1. Start Kiwi Syslog Service Manager.
  2. Navigate to the Kiwi Syslog Server Setup under File > Setup.
  3. Select Inputs > Secure TCP.
    TLS12_kiwisyslog.png
  4. Select the checkbox next to Listen for secure (TLS) TCP Syslog messages.
    • To add a certificate click Select Certificate, and browse to the certificate location.
  5. Under Enabled Protocols, select the checkbox next to TLS 1.2.
    Multiple protocols can be selected.
  6. Click OK.

For more information about secure syslog inputs, see Inputs - Secure (TLS) Syslog.

 

Enable TLS 1.2 for Kiwi Web Access

In addition to enabling and applying the TLS 1.2 protocols in Kiwi Syslog Service Manager, you can also enable SSL support for Kiwi Web Access. Test your web interface by enabling TLS 1.2 only and attempting to connect to the web interface with TLS 1.0 or TLS 1.1.


 

 

 

Last modified

Tags

Classifications

Public