View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000238010000-004: Servicespublic2013-02-19 10:232013-08-20 20:40
ReporterChristian Zugfil Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.02 
Fixed in Version1.03 
Summary0002380: Clarify expected behavior if client sends empty user identity token
Description

It is unclear how a server should respond to an "empty" or user identity token. Is it allowed to use anonymous login as default or should the server return BadUserIdentityTokenInvalid? Both behaviors can be observed in current implementations.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Jim Luth

2013-02-19 17:59

administrator   ~0004472

Last edited: 2013-02-19 18:00

Agreed to fix this by stating in the spec and in a 1.02 ERRATA:
Null or empty user token SHALL always be interpreted as anonymous.

Matthias Damm

2013-08-20 16:09

developer   ~0004936

Added clarification to ActivateSession -> userIdentityToken
Null or empty user token shall always be interpreted as anonymous.
Resolved in document IEC 62541-4 - Services [Pre-CDV] 1.02.02.doc

Jim Luth

2013-08-20 20:40

administrator   ~0004945

agreed to text change.

Issue History

Date Modified Username Field Change
2013-02-19 10:23 Christian Zugfil New Issue
2013-02-19 17:58 Jim Luth Status new => assigned
2013-02-19 17:58 Jim Luth Assigned To => Matthias Damm
2013-02-19 17:59 Jim Luth Note Added: 0004472
2013-02-19 18:00 Jim Luth Note Edited: 0004472
2013-08-20 16:09 Matthias Damm Status assigned => resolved
2013-08-20 16:09 Matthias Damm Resolution open => fixed
2013-08-20 16:09 Matthias Damm Note Added: 0004936
2013-08-20 20:40 Jim Luth Status resolved => closed
2013-08-20 20:40 Jim Luth Note Added: 0004945
2013-08-20 20:40 Jim Luth Fixed in Version => 1.03