ACL: ns=0 standard nodes are ungated, so the "see nothing" boot warning overstates #617

Closed
opened 2026-10-08 02:31:15 -04:00 by dohertj2 · 1 comment
Owner

With Security:Acl:Enabled on, a no-grant principal can still read i=2256 and browse i=2253 — served by the SDK CoreNodeManager, never reaching DataPlaneAuthorizer. The boot warning says it "can connect and see nothing".
Sources: src/Server/ZB.MOM.WW.OtOpcUa.Host/OpcUa/OtOpcUaServerHostedService.cs:265; docs/plans/2026-08-17-perf-followups-r3.md (ACL section).

  • Decide: gate ns=0, or accept + document
  • Correct the boot warning and docs/security.md

Filed 2026-10-08 by the pending/deferred-work sweep after the #562–#591 issue sweep.

With `Security:Acl:Enabled` on, a no-grant principal can still read `i=2256` and browse `i=2253` — served by the SDK `CoreNodeManager`, never reaching `DataPlaneAuthorizer`. The boot warning says it "can connect and see nothing". Sources: src/Server/ZB.MOM.WW.OtOpcUa.Host/OpcUa/OtOpcUaServerHostedService.cs:265; docs/plans/2026-08-17-perf-followups-r3.md (ACL section). - [ ] Decide: gate ns=0, or accept + document - [ ] Correct the boot warning and docs/security.md _Filed 2026-10-08 by the pending/deferred-work sweep after the #562–#591 issue sweep._
Author
Owner

Resolved on master (a6192159).

  • Decision: ns=0 standard nodes stay ungated (served by the SDK CoreNodeManager outside DataPlaneAuthorizer; gating them would break session setup, since clients read them for connection and redundancy health; they carry no plant data).
  • The boot warning in OtOpcUaServerHostedService was corrected ("can still connect and read the standard server nodes ... but sees no plant data") and docs/security.md now has "ns=0 standard nodes stay ungated, deliberately (#617)".

Closed 2026-10-08 by the hardware-available issue sweep (master d898262c).

Resolved on master (a6192159). - [x] Decision: ns=0 standard nodes stay **ungated** (served by the SDK CoreNodeManager outside `DataPlaneAuthorizer`; gating them would break session setup, since clients read them for connection and redundancy health; they carry no plant data). - [x] The boot warning in `OtOpcUaServerHostedService` was corrected ("can still connect and read the standard server nodes ... but sees no plant data") and docs/security.md now has "ns=0 standard nodes stay ungated, deliberately (#617)". *Closed 2026-10-08 by the hardware-available issue sweep (master d898262c).*
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/lmxopcua#617