View Issue Details

IDProjectCategoryView StatusLast Update
000769410000-007: ProfilesSpecpublic2022-08-30 16:39
ReporterDavid_Andover Smith Assigned ToKarl Deiretsbacher  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.05.00 RC1 
Fixed in Version1.05 
Summary0007694: Clarification of differences between CU Security User Access Control Full and Security User Access Control Base
Description

There is only a couple word difference between these two conformance units and the conformance units are not clear on the expected behavior.

Security User Access Control Base (https://profiles.opcfoundation.org/profile/734) says:
"A Server that supports this profile supports restricting some level of access to some Nodes in the AddressSpace based on the validated user."

Security User Access Control Full (https://profiles.opcfoundation.org/profile/691) says:
A Server that supports this profile supports restricting multiple levels of access to all Nodes in the AddressSpace based on the validated user.

As far testing would be concerned, how would that be evaluated during conformance? Wouldn't making parts of the address space available to all users but restricting specific sections constitute multiple levels? Is there a specific number of user access levels to support?

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Karl Deiretsbacher

2022-02-08 17:00

developer   ~0015941

I agree this is confusing. It exists since UA 1.02. We need to see if certification is available.

Karl Deiretsbacher

2022-03-01 17:24

developer   ~0016135

Last edited: 2022-03-05 08:50

Needs to fix text for CUs

  • base is min 2 users, full is more than two users
  • only instance nodes (not those in type system) and not the ones for Namespace 0

Proposal for discussion:
base: https://profiles.opcfoundation.org/profile/1341
full: https://profiles.opcfoundation.org/profile/1732

David_Andover Smith

2022-03-03 12:13

reporter   ~0016153

Can you explain this more with regard to base vs full?

" only instance nodes (not those in type system) and not the ones for Namespace 0 "

Karl Deiretsbacher

2022-08-30 16:39

developer   ~0017469

Fixed in database. The full now requires support for all nodes and configurability.

Jim Luth

2022-08-30 16:39

administrator   ~0017470

Agreed to changes to database.

Issue History

Date Modified Username Field Change
2022-02-01 20:05 David_Andover Smith New Issue
2022-02-08 17:00 Karl Deiretsbacher Note Added: 0015941
2022-02-08 17:23 Jim Luth Assigned To => Karl Deiretsbacher
2022-02-08 17:23 Jim Luth Status new => assigned
2022-03-01 17:24 Karl Deiretsbacher Note Added: 0016135
2022-03-03 12:13 David_Andover Smith Note Added: 0016153
2022-03-05 08:50 Karl Deiretsbacher Note Edited: 0016135
2022-08-30 16:39 Karl Deiretsbacher Status assigned => resolved
2022-08-30 16:39 Karl Deiretsbacher Resolution open => fixed
2022-08-30 16:39 Karl Deiretsbacher Note Added: 0017469
2022-08-30 16:39 Jim Luth Status resolved => closed
2022-08-30 16:39 Jim Luth Fixed in Version => 1.05
2022-08-30 16:39 Jim Luth Note Added: 0017470