ClientUserId – OPC Unified Architecture – Part 5: Information Model

OPC Unified Architecture – Part 5: Information Model

v1.05.06

1Scope
2Normative references
3Terms, definitions, abbreviated terms and conventions
4NodeIds and BrowseNames
- 4.1NodeIds
- 4.2BrowseNames
5Common Attributes
6Standard ObjectTypes
7Standard VariableTypes
8Standard Objects and their Variables
9Standard Methods
10Standard Views
11Standard ReferenceTypes
12Standard DataTypes
Annex ADesign decisions when modelling the server information (Informative)
Annex BDataTypeDictionary (Informative)
- B.1Overview
Annex COPC Binary Type Description System (Informative)
Annex DGeometrical references (Informative)

3.1.1 ClientUserId

String that identifies the user of the client requesting an action

Note 1

Note 1 to entry: The ClientUserId is obtained directly or indirectly from the UserIdentityToken passed by the Client in the ActivateSession Service call or from the authenticationToken in the requestHeader of a SessionlessInvoke Service call. See 6.4.3 for details.