fix(opcuaclient): #910 name the per-endpoint connect budget; widen it in the #816 host-name tests

Cause: the client-side PerEndpointConnectTimeout (3 s), not opc-plc. The
validate:null case is the first test the assembly runs, so it pays the
cold-process cost of the first Basic256Sha256 connect: loading the fresh
throwaway certificate, validating the server's, and the asymmetric handshake.
In the G2 full-solution run that local work used up the budget. The opc-plc
log at 13:13:50-53Z shows the discovery channel closing at 50.709, then nothing
from the client for 3 s, then OpenSecureChannel answered at 53.775 and the
client closing the channel 48 ms later. The SDK reports a wait cancelled by
that budget as BadRequestInterrupted. opc-plc auto-accepted the certificate
(--aa, "Trusting certificate ... command line option") with no reject and no
store round-trip.

- Driver: a per-endpoint budget expiry now surfaces as TimeoutException naming
  PerEndpointConnectTimeout instead of BadRequestInterrupted or a bare
  TaskCanceledException. There is no behaviour change. Unit test added
  against a silent TCP listener.
- Test: the ServerHostNameValidationTests secure options use a 15 s budget,
  the same as the browser integration tests' 10 s. Connect latency is not
  what these tests check.
- docs/drivers/OpcUaClient.md: documents what the budget covers.
This commit is contained in:
Joseph Doherty
2026-11-13 12:42:45 -05:00
parent e299dc090a
commit 73132b7d78
4 changed files with 63 additions and 3 deletions
@@ -35,6 +35,12 @@ public sealed class ServerHostNameValidationTests(OpcPlcFixture sim) : IDisposab
SecurityMode = OpcUaSecurityMode.SignAndEncrypt,
AutoAcceptCertificates = false,
CertificateValidation = new OpcUaCertificateValidationOptions { ValidateServerHostName = validateHostName },
// Gitea #910: the default 3 s per-endpoint budget covers client-side work too — loading the fresh throwaway
// certificate, validating the server's, the first Basic256Sha256 handshake in a cold test process. The first
// test in this assembly (the validate:null case) paid that cold cost, and in the full-solution run it ran out:
// opc-plc answered OpenSecureChannel at once, but the client reached it only after 3 s of local work and
// cancelled 48 ms later (BadRequestInterrupted). What is under test is the host check, not connect latency.
PerEndpointConnectTimeout = TimeSpan.FromSeconds(15),
};
/// <summary>Trust the fixture's server certificate (as advertised on its secure endpoint) in the throwaway PKI.</summary>