docs(index): OtOpcUa master 43f8b8e8 — SDK server logging (#874), SDK2 clock-skew note (#873), integration CI green

2026-11-11 18:08:12 -05:00
parent 1c6fe5793b
commit 81d8901bf0
2 changed files with 3 additions and 1 deletions
@@ -462,3 +462,5 @@ AddRoute of the dev Mac (`oee-tagdump-mac`, `10.181.206.245.1.1`) on the two tes
  - **CI (#871):** two unit-test races that failed hosted runs 1218–1220 fixed (MeshPsk refresh, credential-lockout burst).

 - **2026-11-11 vd03 sister deploys (OtOpcUa itself still `b8b4c18f` there).** mxaccessgw → `2b13564e`, HistorianGateway → `ea9f21c`, ScadaBridge → `424db155`. Consequence: `b8b4c18f`'s Galaxy alarm acks now FAIL against the new gateway (no operator credential; lmxopcua#749) instead of the old silent false success — fixed by deploying OtOpcUa master there (pack: `docs/deploy/vd03-upgrade-b8b4c18f-to-master.md`, preflight #793; needs `Security__ApiKeys__Pepper`, the snapshot-isolation migration, and the SDK 2.0.1 go — #873 clock skew, #874 SDK logging). Galaxy reads/subscribes/host status verified through the new gateway.
+
+- **2026-11-11 master `43f8b8e8`.** #874: the server's OPC UA SDK log output (identity-token/certificate/secure-channel refusals) now reaches the host log, rate-limited. #873 (open): under SDK 2.0.1, API-key logins fail `BadIdentityTokenInvalid` when the client clock is >5 min ahead of the server (RsaEncryptedSecret signing time) — check time sync on every SDK 2 server and client host, **including ScadaBridge once it moves to SDK 2 (ScadaBridge#125)**. #800 partial Windows validation on windev passed (self-contained win-x64 boots, PKI reused across restarts, encrypted reads, refusals correct; no service install). CI: v2-integration hosted-green (run 1225), floor 448.