29
Basisanwendungen
Certificates
Protocols such as HTTPS or OPC UA are based on the TLS protocol. The encryption
of the communication and the authentication of the communication partners is rea-
lized via certificates.
The Web IO identifies itself ex works with a self-signed certificate. Many applica-
tions consider such certificates to be a security risk. If the application requires secu-
re authentication, the Web IO must be equipped with an individual certificate signed
by a trusted certification authority.
Certificate Signing Request (CSR)
Here it is possible to generate a CSR with a new key pair and individual content.
By clicking the
Verify
button, the entered values are formally checked and the new
key is generated. The new CSR can be downloaded via the
Download CSR
button.
Self signed certificate
A previously generated inidividual CSR can be self-signed by the device with
the private key belonging to the CSR.
Upload certificate/upload certificate chain
A previously generated and downloaded CSR can be loaded into the device as a cer-
tificate after signature by an external certification authority. If a certificate chain be-
longing to the certificate is not already part of the certificate file, it can be uploaded
separately afterwards. The files can be in PEM or DER format.
Install certificate/certificate chain
A previously uploaded certificate incl. associated certificate chain is installed in the
device and used as a certificate within TLS connections after saving.
