OPC UA-Connector with Sign&Encrypt

[yannic]

Hey,

we’re currently testing the usage of Solace in our corporate environment.

For testing within Kubernetes, I tried to set up

1. the Solace PubSub+ Event Broker with the Helm chart (this worked fine and MQTT is working).
2. a OPC UA testing server (I used that one: OPC PLC server - Code Samples | Microsoft Learn)
3. the OPC UA connector (https://solace.com/integration-hub/opc-ua/)

The OPC UA connector needs a config file ( application.yml ) that I mounted via a ConfigMap into the Pod where the connector runs in. This works.

The OPC UA test server uses security policy Basic256Sha256 and message security mode Sign & Encrypt . I didn’t find a possibility to set this up in the application.yml that the connector needs.

The demo application.yml offers this options:

opcua:
  java:
    endpointUrl: opc.tcp://localhost:50000 # opc ua server url (ex: opc.tcp://<host>:<port>/<endpoint>)
    username: # opc ua server username
    password: # opc ua server password

I would expect more options than just endpointUrl , username and password . The User-Guide that the Solace OPC UA connector provides, lists a few other options such as connectTimeout or keepAliveInterval . But nothing for the security policy and security mode.

Am I missing something or is this functionality missing in the Solace connector, because this is a common OPC UA feature that we need within our setup.

I hope you can help, thanks in advance!

Yannic

[yannic]

Can no one help here? Is this “feature” not supported by Solace?

[SissyH]

Can you try this… we haven`t tested it heavily so far and it is not documented yet, but should work:

[alcagnetti]

This has been successfully tested with this configuration:

Password “123456” was chosen when generating the client.ptx certificate.

File paths are internal docker path to certificates given this example was tested with Eclipse milo OPC UA demo server docker image.