Search

6 result(s) for UserIdentity

• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.4.2 Session-less Services
  invoked via HTTPS POST. The HTTP Authorization header is used to specify the UserIdentity used to determine what permissions are available to the caller. The Authorization header may specify
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.5.1 Overview
  There is no SecureChannel negotiation when using opcua+json sub-protocol. The default UserIdentity for any Session-less Service calls made over the WebSocket is specified by the opcua+token
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.5.2 Sub-Protocols
  only used in addition to the opcua+openapi sub-protocol and specifies the default UserIdentity for all Requests sent over the WebSocket. The <accesstoken> is the JSON WebToken
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.5.2 External Historical Event Node
  SecurityPolicy used when securing messages for this connection. IdentityTokenPolicy is the type of UserIdentity token that is used for this connection. TransportProfileUri is a string that describes
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.10.9 ApplyChanges
  SecondsTillShutdown and ShutdownReason Properties in the ServerStatus Variable . If a TrustList change only affects UserIdentity associated with a Session then Servers shall re-evaluate the UserIdentity
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  9.1 Overview
  Server are used to populate an AccessToken with the Roles associated with the UserIdentity provided when the Client submits the request. This scenario is illustrated in Figure 29 . Figure