fix(security): the ACL startup warning described stage 5's scope, not stage 6's
It told the operator "Read, Browse and Subscribe remain ungated" — which stage 6 is precisely the change to. A warning that misstates what a security control does is worse than no warning, because it is read as authoritative. Claude-Session: https://claude.ai/code/session_015p7wGqy3YpZNCpDzTpGMKo
This commit is contained in:
@@ -243,8 +243,9 @@ public sealed class OtOpcUaServerHostedService : IHostedService, IAsyncDisposabl
|
|||||||
if (_dataPlaneAuthorizer is { Enabled: true })
|
if (_dataPlaneAuthorizer is { Enabled: true })
|
||||||
{
|
{
|
||||||
_logger.LogWarning(
|
_logger.LogWarning(
|
||||||
"OtOpcUaServerHostedService: node ACL enforcement is ENABLED — writes, alarm commands and "
|
"OtOpcUaServerHostedService: node ACL enforcement is ENABLED — EVERY data-plane operation "
|
||||||
+ "HistoryRead now require a matching NodeAcl grant. Read, Browse and Subscribe remain ungated.");
|
+ "(read, browse, subscribe, write, alarm commands, HistoryRead) now requires a matching "
|
||||||
|
+ "NodeAcl grant. A principal with no grant can connect and see nothing.");
|
||||||
}
|
}
|
||||||
|
|
||||||
// Propagate the configured tie-cluster over-fetch bound onto the node manager so HistoryRead-Raw
|
// Propagate the configured tie-cluster over-fetch bound onto the node manager so HistoryRead-Raw
|
||||||
|
|||||||
Reference in New Issue
Block a user