[oscerd]

Backport of #27824, with the test follow-up #27999, onto camel-4.18.x.

Original PRs: #27824 - CAMEL-25645: camel-milo - let the OPC UA client validate the server certificate against a trust list, and #27999 - CAMEL-25645: camel-milo - ServerCertificateValidationTest writes the value before the consumers start
Target branch: camel-4.18.x

CAMEL-25645

What it does

As on main, milo-client and milo-browse validate the certificate of the OPC UA server when the selected endpoint uses a security policy other than None:

• New options:
  • trustListDirectory: Milo's file based trust list. It checks the chain, the validity period, the revocation status and the application URI. A CA-issued certificate needs a CRL of its CA in the trust list.
  • certificateValidator: a custom validator.
  • trustAllCertificates.
• Without trust configuration, the client does not connect to such an endpoint, and logs a WARN that says why.
• The same validator checks the certificate that the user name and password are encrypted with.
• The last connection failure is the cause of No connected.

Adaptations for camel-4.18.x

The milo client code on this branch differs from main, so this is a hand port of the final state of #27824. It needs a review:

• @UriParam has no security attribute on this branch, so trustAllCertificates is not marked insecure:ssl. There is no SecurityUtils registry to regenerate, and no catalog doc copies.
• The user name and password only come from the endpoint URI on this branch (there are no username/password options). The validator is passed to that single UsernameProvider.
• SubscriptionManager uses synchronized blocks instead of a lock, and MiloClientConfiguration.clone() is the copy constructor, which now copies the new options.
• The connection cache id does not contain the requested publishing interval. The trust settings are appended to this branch's id.
• Eclipse Milo 1.1.1 on this branch has every API the change uses.
• The upgrade guide note for this branch goes into the 4.18 guide on main, in the 4.18.6 section.

Tests

• camel-milo: 58 tests, 0 failures, 1 skipped (MonitorItemMultiConnectionsCertTest, already @Disabled), including ServerCertificateTrustTest, MiloClientConfigurationTest and the end-to-end ServerCertificateValidationTest.
• A full reactor build of the branch.

Claude Code on behalf of Andrea Cosentino

🤖 Generated with Claude Code

[davsclaus]

Thanks @oscerd.

This port is adapted, so it was reviewed against 1109759 plus the test fix eb14b16 (#27999), which is folded in here. Each difference from main comes from code or API that camel-4.18.x lacks:

• trustAllCertificates has no security = "insecure:ssl". The @UriParam on 4.18.x has no security attribute, and the branch has no SecurityUtils or security policy framework. That also explains why the SecurityUtils owner map change is left out. So on 4.18.x trustAllCertificates=true is not reported by a prod profile, but the default is still false and the client still refuses to connect without trust settings.
• SubscriptionManager passes the validator to the only UsernameProvider the branch has, the one built from the URI user info. Main's explicit username/password provider and its creds.length == 2 ? creds[1] : "" empty-password handling come from CAMEL-23812 (58f5ca7), not from CAMEL-25645, so leaving them out is correct. The identity token check is complete for 4.18.x.
• lastConnectFailure is set in the branch's synchronized handleConnectionFailure rather than inside main's lock, so the behaviour is the same.
• toCacheId() and MiloClientConfigurationTest keep the branch's cache id without requestedPublishingInterval. The trust settings appended to it are the same as on main.
• The catalog doc copies are not touched, because 4.18.x does not mirror component docs into the catalog.

ServerCertificateTrust, the docs and the three tests are the same as on main. Branch Milo is 1.1.1, still on the 1.x API. The generated files are consistent: both component JSON copies are identical, indexes are sequential, the three options show up at component and endpoint level, and the configurers, URI factories, component DSL and endpoint DSL are all regenerated. CI is green. The incremental build ran camel-milo (58 tests, 0 failures), including ServerCertificateValidationTest, ServerCertificateTrustTest (13 tests) and MiloClientConfigurationTest.

The upgrade guide note for this behaviour change (a client that used to connect to a Sign/SignAndEncrypt endpoint without trust settings now refuses to connect) is in #28055 on main, under "Upgrading from 4.18.5 to 4.18.6". That one can be merged once this is in.

LGTM.

Claude Code on behalf of Claus Ibsen