Correct obsolete AllowAnonymous per-node authorization remarks #722
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
OpcUaApplicationHostOptions.AllowAnonymous XML remarks still say per-node enforcement has not landed and reads carry no authorization check. That is obsolete source documentation and can mislead operators about admission versus authorization.
Source at
c8e3e279b4:Correct only the stale remarks to describe current behavior: AllowAnonymous controls admission; authorization depends on enabled per-node enforcement and the principal's grants, with the disabled legacy mode stated accurately. Preserve the deliberate true default, endpoint/session behavior, runtime code and assertions. Do not claim production ACL rollout or client acceptance from source evidence. Peer URI/redundancy comments are already tracked by #717 and are outside this correction.
Documentation-only verification: review against current authorizer/Read source, ensure declaration and executable code unchanged, check diff. No live calls or full solution rerun needed. No implementation has started.
The approved documentation-only correction is verified and committed locally as 1643b63c, also integrated into the pending #721 batch as
f478b844. AllowAnonymous now distinguishes admission from the current per-node ACL checks: a wired, enabled authorizer gates reads and denied reads return BadUserAccessDenied; a disabled or unwired authorizer retains the legacy read path. The default remains true.Root independently checked the admission, authorizer and Read paths; git diff --check passed and all non-XML-comment bytes match the previous version. Only the approved remarks changed; no runtime, configuration, assertions or live calls changed. No test was added for human prose.
Publication is sequenced after #719 final-head CI983 so a new push cannot supersede its queued gate. This issue stays open until the verified documentation is merged; it will travel with the approved #721 batch.
Published reviewed fixes in PR #724, head
e1feb9fbb6, based on merged #719 master1bf8c614. The ancestry merge preserves tree618eb2d3e7exactly: integrated actor suite 35/35, independent review clear; earlier full Runtime 833 passed/3 existing skips before integration. No redundant local full-solution rerun or live calls.Required final-head hosted run #985/job3606 is queued behind main run #984/job3605. Merge/closure wait for #985 success, floor and artifacts. Production Warm behavior is outside this fix.
Merged PR #724 as
c89912a93bafter hosted run 986 passed all ten steps at final headc4b4046832. The merged tree exactly equals the tested head tree (973c6799d1). CI verified 14,656 executed tests across 62 TRX files, 573 skips, the 12,000-test floor and artifact upload. #721 and #722 are resolved. The independently reproduced intermittent ConditionRefresh failure remains tracked in open #728. No live calls or Warm implementation.