Protecting Web Access Via Ssl; Installing A Certificate; Creating A New Certificate And Having It Signed - CheckMK Rail2 Mark I Manual

Check_MK rail2 Mark I - Manual 22 / 57

8. Protecting web access via SSL

Access to your device's web interface is factory-set to take place via HTTP in plain text. You can protect
this access via HTTPS (SSL), encrypting the data transferred between your browser and the device.
You can open the configuration by pressing the button Web access type in the device settings.
8.1 Installing a certificate
In order to encrypt data traffic, the device needs a certificate and a private key first. There are several
ways available for you to install these.
• Create a new certificate and have it signed by a certification authority by sending a certificate signing
request (CSR)
• Upload an existing private key and certificate
• Create a new certificate and sign it yourself
You can choose one of the options above that fits your requirements and possibilities. Certificates signed
by certification authorities generally have the advantage that clients can automatically verify the au-
thenticity of the host (device) at the time of access. This is normally the case with official certification
authorities.
If a user accesses the web interface via HTTPS and the certificate is either self-signed or signed by a
certification authority not trusted by the user, this will cause a warning to appear in the user's web
browser first.
8.1.1 Creating a new certificate and having it signed
To create a new certificate, select the option New certificate. In the dialogue box that follows, you now
enter device and operator information, which is then stored on the certificate and can be used by both
the certification authority and clients later on to verify the certificate.
©Copyright Mathias Kettner GmbH 2018 mathias-kettner.de