Control Panel
24/64
ð
As an administrator you can now use the control panel, create further
users in the user management, and assign access rights.
Also see about this
2
User management [
}
38]
8.1.2
Secure connection
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
[
}
page 42]).
netPI | NOIT-E-NPI3-51-EN-RE
DOC170801UM01EN | Revision 1 | English | 2017-09 | Released | Public
© Hilscher 2017
