keep the structure of node and its aggregates browsable by every session, leaving every
other permission as declared.
A node whose RolePermissions grant Browse to neither Anonymous nor AuthenticatedUser is
hidden from any session that holds none of the roles it names. Where those roles are ones
the server never assigns, nobody sees the node, and its parent - browsable by everyone -
shows an instance missing the mandatory children of its type. Opc.Ua.NodeSet2.xml does
this to eleven nodes under Server/PublishSubscribe (the methods of SecurityGroups and
KeyPushTargets, with their arguments), reserved to the SecurityKeyServerAdmin role
(CTT Base Info Core Structure 002, FEAT-30).
Such a node gains Browse for Anonymous and AuthenticatedUser, which every session's
permissions are evaluated against; Read, Write and Call stay with the roles it named. A
node without RolePermissions, or that already grants Browse to one of the two, is left as
it is.
keep the structure of
nodeand its aggregates browsable by every session, leaving every other permission as declared.A node whose RolePermissions grant Browse to neither Anonymous nor AuthenticatedUser is hidden from any session that holds none of the roles it names. Where those roles are ones the server never assigns, nobody sees the node, and its parent - browsable by everyone - shows an instance missing the mandatory children of its type.
Opc.Ua.NodeSet2.xmldoes this to eleven nodes under Server/PublishSubscribe (the methods of SecurityGroups and KeyPushTargets, with their arguments), reserved to the SecurityKeyServerAdmin role (CTT Base Info Core Structure 002, FEAT-30).Such a node gains Browse for Anonymous and AuthenticatedUser, which every session's permissions are evaluated against; Read, Write and Call stay with the roles it named. A node without RolePermissions, or that already grants Browse to one of the two, is left as it is.