Secure Connection - hilscher NIOT-E-TPI51-EN-RE User Manual

Netiot edge gateway
Hide thumbs Also See for NIOT-E-TPI51-EN-RE:
Table of Contents

Advertisement

Control Panel
8.1.2

Secure connection

Edge Gateway | NIOT-E-TPI51-EN-RE (Connect)
DOC170502UM07EN | Revision 7 | English | 2019-07 | Released | Public
Ø Click Change Password only after the entered password has been
evaluated as strong.
ð The administrator password for the user account Admin has thus been
changed.
ð As an administrator you can now use the control panel, create further
users in the user management, and assign access rights.
Edge Gateways support web connections secured by SSH/TSL via
https:// accesses only.
By definition, a secure connection can provide an efficient protection only if
a certificate proves that the server is secure. Only then can running
transactions of the initiating browser and the server be considered as
protected against interception and data theft.
This is why the browser at first inquires a certificate of verification from the
server (Gateway). This certificate proves that the issuer has verified the
security of the server. Each browser provides a preinstalled list of known
authorized issuers of certificates.
Each time the certificate of the server arrives at the browser, the browser
compares the issuer of the certificate with the issuers stored in the list of
known authorized issuers of certificates.
If the issuer of the certificate is not listed, the browser will signal a
certificate error and request the user's confirmation to continue because it
assumes that the connection is insecure.
As standard, Edge Gateways contain a certificate issued by Hilscher that is
not on the list of the known authorized issuers of certificates. Due to that,
the browser signals an insecure connection and requests the confirmation
to continue. When this confirmation has been given once, any future
connections will be established without further requests.
Note:
In the control panel you can replace this certificate any time by the
certificate of a known authorized issuer of certificates, see section
Uploading and installing own security certificates).
27/294
© Hilscher 2017 – 2019

Advertisement

Table of Contents
loading

Table of Contents