Symbol:
Function: The tab allows for the configuration and the transfer of controller certificates for encrypted communication with the controller.
Call: Menu bar: “View”
The “Devices” tab shows all PLC devices configured in the project and their certificate store. If the communication path to the controller is configured, then you see the certificates that are stored in memory. Here you can create and configure new certificates on the controller. If a certificate currently in use is about to expire, then you get a warning when you log in to the device. From there you can also switch directly to the “Security Screen” to renew the certificate.
Left side: “Information” |
Devices and certificate store Shows the individual devices |
Toolbar (left side) |
|
Right side: “Information” |
If the active path to the controller is set and a device node is selected, then every use case for controller certificates is displayed on the right side.
As long as a certificate is not available for one of these use cases, it is displayed
with the When a certificate store is selected on the left side, all certificates in it are displayed on the right side with the following information: “Information”: Use case (currently the controller component in question is displayed: for example “CmpSecureChannel”.) “Created for”: Name of the computer for which the certificate was created (for example, “MyLocalPC”) “Created by”: Name of the computer on which the certificate was created (for example, “MyLocalPC”) “Valid as of”: Date (for example, “07/20/2017 15:09:29”) “Valid until”: Date (example: “07/20/2022 00:00:00”. Depending on the remaining time of the certificate, the highlight color of the field changes: green -> yellow (two-thirds expired) -> orange (nine-tenths expired) -> red (expired). Note: When logging in to the controller, you get a warning when two-thirds or more of the validity period have expired. Then you can renew the certificate here in the “Security Screen”. “Thumbprint”: Hash value from specific properties of the certificate for purposes of identification (for example, “279e1a46b86bd636c8e6f19fd51c222469ec49a8”) This thumbprint can be used together with the Mqtt library. Refer to the Mqtt library documentation in the Library Manager. Double-clicking a certificate entry opens the default Windows “Certificate” dialog. As a result, you can import a controller certificate into the Windows Certificate Store in the “Controller Certificates” folder, so that it is available for the encryption of boot applications, downloads, and online changes. If multiple certificates are available for one use case, then the system follows the steps below to determine the certificate that is used:
|
Drag&Drop: Moving of the certificate to another certificate store of the same device Double-clicking a certificate entry opens the default Windows dialog for displaying all certificate information. |
|
Toolbar (right side) |
The “Certificate Settings” dialog opens for configuring the “Validity period” of the certificate and the “Key length” for the private key. Clicking “OK” saves the specified values in the CODESYS options. The values are reset at the next operation. As long as the certificate is being created, "“(computing)”" is shown after the use case. You cannot cancel the creation operation, but you can close and continue working with the “Security Screen”.
I
|