Replies: 1 comment 4 replies
-
you need to distinguish between transport security (e.g. Sign&Encrypt) and UserAuth via Certificates (peer-certificate) each OPC UA Application needs a own x509v3 Instance-Certificate with the subjectAltName-Extension! (and a private-key of course) |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I tried using the server and client examples of encryption, but they didn't work. In theory, I need to create my own certificates with OpenSSL and the example in the repository. However, I don't understand how they work. In the server, you add a user to a certificate named "peer-certificate-example-1.der" and then load the certificate and private key called "certificate-example" and "private-key-example", respectively. In the client, to connect, I need to use the first certificate and the key "peer-certificate-example-1" and then add the server's certificate "certificate-example" in "set_security".
I think the client needs a certificate with a key ("peer-certificate-example-1") and the server needs another one ("certificate-example/private-key-example"), and then they need to read each other's certificates. However, I don't understand whether I need to do something specific for the client and something else for the server, or just make two copies of the same certificate but with different names.
I've tried making my own certificates and keys, but nothing seems to work. I also don't know if in the server when I set the "name" it's something from the certificate or I can write anything and when I create the certificate I don't know if in "subjectAltName = " I need to write the server endpoint "opc.tcp://localhost:4840/freeopcua/server/".
Beta Was this translation helpful? Give feedback.
All reactions