docs(history): ScadaBridge OPC UA client on SDK 2.0.1 (ScadaBridge#125 closed, a2e9d718)

Claude-Session: https://claude.ai/code/session_01GT67ACmpMR7b9LGRPLijMi
This commit is contained in:
Joseph Doherty
2026-11-12 22:24:07 -05:00
parent 41a5e4d187
commit 2859d9ebfc
@@ -17,3 +17,18 @@
- Failover passes 8/8 legs, with the same timings as on the old client. - Failover passes 8/8 legs, with the same timings as on the old client.
- **Operational note:** since .156, a CA-issued OPC UA server cert that the DCL trusts needs an issuer with `keyCertSign`. SDK self-signed certs are unaffected. - **Operational note:** since .156, a CA-issued OPC UA server cert that the DCL trusts needs an issuer with `keyCertSign`. SDK self-signed certs are unaffected.
- **2.0.x is deferred** until lmxopcua#799 and #801 close. #125 stays open to track it. - **2.0.x is deferred** until lmxopcua#799 and #801 close. #125 stays open to track it.
- **2026-11-12 OPC Foundation SDK 1.5.378.182 → 2.0.1 (`main` `a2e9d718`, ScadaBridge#125 closed; not deployed).** Done once lmxopcua#782/#799/#801 had closed. Client (DCL) and the test-only Server move in lockstep; the transitive Core/Core.Types/Types/Configuration/Security.Certificates packages resolve to 2.0.1.
- **API breaks fixed (DCL only):**
- Immutable `Variant`/`DataValue`/`NodeId`/`StatusCode` and `ArrayOf<T>`. New `OpcUaValueBoundary` restores the SDK 1.5 CLR value shapes (`byte[]`, UTC `DateTime` with no-timestamp = `MinValue`, `Guid`, detached arrays) and keeps `new Variant(object)` write semantics.
- `StatusCodes` are no longer constants, so code matches them by value.
- `CertificateIdentifier.Certificate` and the `CertificateValidation` event are gone. The SDK-created `CertificateManager` owns the identity and trust lists and is disposed with the session; auto-accept and the verify probe use `AcceptError`.
- X509 user identity now goes through `X509IdentityTokenHandler`.
- **UserName = `LegacyRsaUserNameIdentityTokenHandler`** (ported from OtOpcUa `be28aa44`, lmxopcua#880). SDK 2's default handler sends a 65-char API key as an `RsaEncryptedSecret`, which SDK 1.5 servers reject (`BadIdentityTokenInvalid`) and SDK 2 servers clock-gate (#873). The DCL sends what it sent on 1.5, so it works against both server generations in a mixed rollout.
- **Operational:** SDK 2 never accepts an incomplete chain or an empty subject/issuer DN, even with `AutoAcceptUntrustedCerts`. The `keyCertSign` rule from .156 still applies.
- **Tests:** Release 0 warnings; DCL 570/570 incl. the #121 secure-connect tests and opc-plc live tests. The new handler tests are mutation-checked. Whole solution 11,345 passed / 188 failed (185 Playwright with no browser server, 3 load flakes that pass in isolation).
- **Wire-compat re-run:** lmxopcua harness, its key now the 65-char production shape (`2705f166`). Against baseline `83ed880e` (SDK 1.5) and master `412da27c` (SDK 2.0.1):
- Matrix 11/11 ×3 modes on both servers, ACL off and on; 8 trust controls fail closed.
- Failover 8/8. Kill reaches the backup in about 20 s as before; freeze is detected in about 15 s (was about 20 s).
- A mutation run with the SDK default UserName handler fails every SDK 1.5 leg with `BadIdentityTokenInvalid`, which is #880 reproduced from the consumer side.
- Evidence: `~/validation-evidence/scadabridge-125/client-2.0.1/` (contains private PKI; not committed).