Public Key Infrastructure
239/263
16.5.2
Working with key files for HTTP and OPC UA Server
16.5.2.1
Uploading a key file for a server certificate into the Edge Gateway
Note:
If at one point in time, you intend to upload both a client
authentication certificate and the related private key file, always
upload the key file
key.pem
first and then upload the certificate file
cert.pem
into the Edge Gateway.
To upload a key file for a server certificate for the communication with the
HTTP server, Node-RED, the Edge Server or the REST API from a file into
the Edge Gateway, proceed as follows.
Ø
Select option
Service certificates
in selection list (Selection list Root/
Service Certificates).
Ê
In window
Certificates
, a tree structure is displayed instead of the
former display of the contents of the Linux trust store.
If the server certificate applies to the communication with the HTTP server,
Node-RED, the Edge Server or the REST API:
Ø
Within window
Certificates
, select the entry
key.pem
below
nginx
.
Alternatively: If the server certificate applies to the communication with the
OPC UA-Server or mosquitto:
Ø
Within window
Certificates
, select the entry
key.pem
below
opcua
.
Ê
The window
Certificate Viewer
is empty.
Ø
Click at button
Upload
in the header of window
Certificates
.
Ê
A file selection dialog appears:
Ø
Within that dialog, select the key file to be uploaded!
Ê
A confirmation prompt appears and indicates the danger of irreversibly
overwriting the current certificate file when continuing.:
Ø
If you are really sure to need the current certificate file not any longer,
click at
Yes
.
The key file is being uploaded into the Edge Gateway.
Note:
If you upload a server certificate for the communication with the
HTTP server, Node-RED, the Edge Server or the REST API from a
file into the Edge Gateway , a reboot of the Edge Gateways is not
necessary.
Edge Gateway | NIOT-E-TIB100-GB-RE (Remote)
DOC170501UM04EN | Revision 4 | English | 2018-08 | Released | Public
© Hilscher 2017 – 2018