Owner decision: turn on OPC UA server-certificate host-name validation by default? #837
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
From #816.
certificateValidation.validateServerHostName(and CLI--validate-host-name) is opt-in and unset = off, preserving behaviour for NAT/IP-addressed deployments. It only applies to Sign/SignAndEncrypt sessions. Decide whether new configs (or all) should default to on, and whether the AdminUI should surface it more prominently. Known caveats documented in docs/drivers/OpcUaClient.md: IPv6 zone ids, loose first-label matching in the SDK.Owner decision 2026-11-11: keep opt-in.
validateServerHostNamestays off when unset for both new and existing configs. Remaining work is docs/AdminUI only: show the toggle and its NAT/IPv6 caveats prominently. Then close.Done (owner decision: keep opt-in). The host-name check toggle moved to the Security panel with help text covering the NAT/IP, IPv6-zone and loose-match caveats. docs/drivers/OpcUaClient.md records the decision. Pushed to master in
e857135e..7a27ef1f; full suite green (20 projects, 0 failures, 0 warnings).