This example shows how to create the necessary certificates (root, server and client certificate) using XCA:
1. Create 3 private keys (for example: rootKey, serverKey and clientKey( this keys are necessary for the certificates))

(all 3 keys are generated with the same conditions but different names)

2. Create a root-, a server- , and a client-certificate
Root-certificate:
- select "[default]CA" and click on "apply all":

- switch to "Subject" and fill out the fields.
Important: Internal Name & commonName should be unique in
each certificate:
You can select the before created key for the root certificate or you can also create a new one:

- switch to "Extensions" and select "Certification Authority" and activate both "Key identifier":

- switch to "Key usage" and select "Certificate Sign and CRL Sign" and click on "OK" ( the root certificate will be created):

Server -certificate:
- click on the root certificate and select "New Certificate":
- select "[default] TLS_server" and click on "apply all":

- switch to "Subject" and fill out the fields. Important: Internal Name & commonName should be unique in each certificate:
You can select the before created key for the server certificate or you can also create a new one:

- switch to "Extensions" and select "End Entity" and activate both "Key identifier":

- switch to "Advanced" and enter the "subject alternative name" with the following syntax:
subjectAltName=URI:urn:[FQDN:Port], DNS:[FQDN]
For example:
- and click on "OK"
Client -certificate:
- click on the root certificate and select "New Certificate":

- select "[default] TLS_client" and click on "apply all":
- switch to "Subject" and fill out the fields. Important: Internal Name & commonName should be unique in each certificate:
You can select the before created key for the client certificate or you can also create a new one:
- switch to "Extensions" and select "End Entity" and activate both "Key identifier". In addition, click on "edit" and add a "subject alternative name".
the syntax is the following: URI:urn:[FQDN]
For example:
- afterwards click on OK
All certificates are created:

3. Export the server - and the client key ( it is not necessary to export the root-key)
the order does no matter
- select the right format (.pem) and enter the right file extension:
4. Export the all certificates (root, server and client)
Export the root certificate:
- select the root certificate and click on "Show Details":

- switch to "Subject" and copy the Hash. Click on "Cancel" and select "Export":

- after exporting, rename the root certificate.
syntax: [hash.0] :
For example:

Export server- and client certificate:
- click on server - or on client certificate (the order does no matter) and click on "Export".
Both certificates must have the extension “.der”.
The correct format must therefore be selected and the correct extension entered:

so now, all certificates + all keys are created and exported
-----------------------------------------------------------------------------------------------------------------------------
Switch to the server PC:
1. open the following path" C:\ProgramData\COPA-DATA\System\PKI\CA\certs" and insert (via copy and paste) the server- and the root - certificate:
2. open the settings of the PG, switch to endpoints and click on "..." of the server certificate and insert it (via copy and paste). select it:

3.
click on "..." of the server server private key and instert it (via copy and paste). select it:

Connect to client- PC
1. open the following path of the client-PC "C:\ProgramData\COPA-DATA\System\PKI\CA\certs"
and insert (via copy and paste) the client- and the root - certificate:

2. insert it (via copy and paste) the client certificate. Choose it:
3. Insert (via copy and paste) the client private key and select it:
Afterwards, you can read the PLC variables in background and can import the desired variables