View Issue Details

IDProjectCategoryView StatusLast Update
000632910000-014: PubSubSpecpublic2021-03-30 15:53
ReporterMatthias Damm Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0006329: SetSecurityKeys needs clarification for SecurityGroupId
Description

We define the SecurityGroupId as unique inside a SKS (see also 0006328).

But in the SetSecurityKeys method, only the SecurityGroupId is passed in. There is no identification of the corresponding SKS.
In all other places we have a relation to the SKS

  • WriterGroup, ReaderGroup and DataSetReader configuration (SecurityKeyServices as EndpointDescriptions)
  • GetSecurityKeys (is called on the SKS)
TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0006328 closedMatthias Damm Uniqueness of SecurityGroupId and SKS identification 

Activities

Matthias Damm

2021-03-04 21:04

developer   ~0013982

9.1.3.3 SetSecurityKeys
Added the following clarification:
The OPC UA Client calling this Method shall be the SKS application with the ApplicationUri that matches the ApplicationUri in the SecurityKeyServices parameter of the WriterGroup, ReaderGroup or DataSetReader objects using the SecurityGroupId.

Added in
OPC 10000-14 - UA Specification Part 14 - PubSub 1.05.0 Draft31.docx

Jim Luth

2021-03-30 15:53

administrator   ~0014134

Agreed to changes in 1.05 and 1.04 Errata.

Issue History

Date Modified Username Field Change
2020-12-30 12:04 Matthias Damm New Issue
2020-12-30 12:04 Matthias Damm Relationship added related to 0006328
2021-03-03 16:50 Matthias Damm Assigned To => Matthias Damm
2021-03-03 16:50 Matthias Damm Status new => assigned
2021-03-04 21:04 Matthias Damm Status assigned => resolved
2021-03-04 21:04 Matthias Damm Resolution open => fixed
2021-03-04 21:04 Matthias Damm Note Added: 0013982
2021-03-30 15:53 Jim Luth Status resolved => closed
2021-03-30 15:53 Jim Luth Fixed in Version => 1.05
2021-03-30 15:53 Jim Luth Note Added: 0014134