![Avatar](https://opcfoundation.org/wp-content/uploads/sp-resources/forum-avatars/defaults/userdefault.png)
08/22/2018
![sp_UserOfflineSmall](https://opcfoundation.org/wp-content/sp-resources/forum-themes/reboot/images/darkpack/sp_UserOfflineSmall.png)
We're introducing OPC UA to our site. We have a simple OPC UA server and OPC UA client.
The OPC UA Server (Matrikon OPC UA Tunneller) and the test client we're using (Prosys OPC UA Client) where simple to set up.
The Transport Security is set to Sign & Encrpy on both sides. No issues with that.
The Application Security was also easy - the OPC UA client attempted to connect and subsequently failed - however, the OPC UA server configuration software detected the client attempting to connect and allowed me to move the client certificate from the rejected store to the trusted store. Once that was done, the OPC UA client connected.
For the User Security component - when using 'Anonymous or Username/Passwords - there are no problems connecting.
Where I am having difficulty in understanding is the User Security component when attempting to use Certificates and Private Keys. My initial questions are:
- How do I generate this certificate and public key?
- Should we just use Username/Passwords for User Security?
- Where can I find the OPC Configuration Tool? It seems to be referenced a lot, but I can't find the actual tool to download.
I did find the Opc.Ua.CertificateGenerator.exe tool on the OPC UA server. In command prompt, I used the following parameters.
Opc.Ua.CertificateGenerator.exe -cmd issue -sp . -an OPCTEST-o MyCompany -pw password -pem true,
This generated the type of files that seemed to be recognised on the OPC UA Client interface (.der for the certificate and .pem for the private key). However, when using the password, the Client produced an error when trying to read the private key (possibly just a bug with the OPC UA client?)
Am I on the right track here? Am I over thinking this? Note: The data is important to our operation, and as we will be allowing data to be written to the control system, we want to make this as secure as possible.
![Avatar](https://opcfoundation.org/wp-content/uploads/sp-resources/forum-avatars/defaults/admindefault.png)
05/30/2017
![sp_UserOfflineSmall](https://opcfoundation.org/wp-content/sp-resources/forum-themes/reboot/images/darkpack/sp_UserOfflineSmall.png)
The UA client needs to be configured with the private key password you supplied.
Please check the client documentation.
Note that some clients do not support private key passwords, however, they should.
The configuration tool was specific to the OPC-F .NET samples. It is no longer available as a binary.
Opc.Ua.CertificateGenerator.exe is a tool you can you, however, make sure you update it regularly from whatever supplier provided it.
The source is on GitHub here:
1 Guest(s)