View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0009611UA SpecificationSpecpublic2024-06-18 09:212024-06-18 15:21
ReporterNathan Lebeau Assigned ToJeff Harding  
PrioritynormalSeverityminorReproducibilityhave not tried
Status assignedResolutionopen 
Product Version1.05.03 
Summary0009611: Browse permission management should be clarified in specification
Description

OPC UA 1.05 part 3 §8.55 specifies for the Browse permission: "The Client is allowed to see the references to and from the Node.".

First, does it mean that the client shall have the permission on the source node to browse, AND on all its references target nodes ?
It seems to be confirmed by the following answer on the forum: https://opcfoundation.org/forum/opc-ua-standard/what-does-it-mean-for-an-object-to-not-be-browsable/

Secondly, how to manage in the browse service the case of target node for which permission is not granted (but it is for source node) ?
I guess the only choice is to remove silently the reference from the References array of BrowseResult even if it is part of "The set of references that meet the criteria specified in the BrowseDescription." (part 4 §7.6).
If you confirm this is the expected behavior, I think the BrowseResult description should indicate it also depends on target node permissions.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Jeff Harding

2024-06-18 15:21

developer   ~0021375

The description should be updated to ensure it is clear that Browse permission for both the source and target nodes are needed for the reference to be included in the browse results

Issue History

Date Modified Username Field Change
2024-06-18 09:21 Nathan Lebeau New Issue
2024-06-18 15:20 Jim Luth Assigned To => Jeff Harding
2024-06-18 15:20 Jim Luth Status new => assigned
2024-06-18 15:21 Jeff Harding Note Added: 0021375