View Issue Details

IDProjectCategoryView StatusLast Update
000457710000-007: ProfilesSpecpublic2020-09-22 16:08
ReporterPaul Hunkar Assigned ToPaul Hunkar  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Summary0004577: Need to add conformance unit for User switch
Description

A conformance units should be defined that describes allowing a client to change the User that is connected on a connection (both a client and server conformance unit)

Server - In the security bucket
Supports, via Activate Session, the changing of the logged-in user. I.e. changing from Operator to Administrator or other user on an active session. This includes reprocessing of any subscription to ensure that only authorized data is supplied.

Client
Can change the user associated with an existing session, by issuing an activate session with new user credentials. This includes being able to handle that the change might be refused and/or that items in subscription might report User access denied.

These conformance units should be added as optional to the standard server and standard client profiles

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0006083 closedMatthias Damm 10000-004: Services Need to add conformance unit for User switch 

Activities

Karl Deiretsbacher

2019-06-25 15:39

developer   ~0010403

Such CUs already exist:
SERVER: See "Session Services" --> "Session Change User" in "Standard 2017 UA Server Profile"
CLIENT: See "Session Services" --> "Session Client Impersonate" in "Core 2017 Client Facet"

Jim Luth

2019-06-25 15:53

administrator   ~0010404

Propose adding the server CU to other Server Profiles as optional.

Karl Deiretsbacher

2020-09-17 17:23

developer   ~0012924

Last edited: 2020-09-22 16:06

Discussed in UA virtual F2F on 2020-09-17. Fixed v1.03 and v1.04 as follows:
The CU "Session Switch User" was moved from Standard UA Server to the Core Server Facet as optional.

Jim Luth

2020-09-22 16:08

administrator   ~0012973

Agreed changes in 1.03 and 1.04 databases (no Errata).

Issue History

Date Modified Username Field Change
2019-01-04 20:28 Paul Hunkar New Issue
2019-06-25 15:39 Karl Deiretsbacher Note Added: 0010403
2019-06-25 15:53 Jim Luth Note Added: 0010404
2019-06-25 15:53 Jim Luth Assigned To => Paul Hunkar
2019-06-25 15:53 Jim Luth Status new => assigned
2020-09-17 17:23 Karl Deiretsbacher Status assigned => resolved
2020-09-17 17:23 Karl Deiretsbacher Resolution open => fixed
2020-09-17 17:23 Karl Deiretsbacher Note Added: 0012924
2020-09-22 16:03 Jim Luth Issue cloned: 0006083
2020-09-22 16:03 Jim Luth Relationship added related to 0006083
2020-09-22 16:06 Jim Luth Note Edited: 0012924
2020-09-22 16:08 Jim Luth Status resolved => closed
2020-09-22 16:08 Jim Luth Fixed in Version => 1.04
2020-09-22 16:08 Jim Luth Note Added: 0012973