Search

9 result(s) for Client,

• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.2.3 Resource Exhaustion
  typically valid, but they each use up a resource resulting in a single Client obtaining all resources blocking valid Clients from accessing the Server . For example, on a Server ... which only 10 Sessions are available a malicious person using a legitimate Client, could obtain all 10 Sessions . Or a malicious Client could try to open 10 SecureChannel s, without
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.4 Message spoofing
  feigning identities (user, application, process etc.). An attacker could forge Message s from a Client or a Server or a Publisher where the messages are forged to attempt to appear ... occur at multiple layers in the protocol stack. By spoofing Message s from a Client, a Server or Publisher , attackers can perform unauthorized operations and avoid detection of their activities
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.7.7 Verifying Message Security
  transport error Message before closing the channel. Once the channel is closed the Client shall attempt to re-open the channel and request a new SecurityToken by sending an OpenSecureChannel ... request. The mechanism for sending transport errors to the Client depends on the communication channel. The receiver shall first check the SecureChannelId . This value may be 0 if the Message
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.5.2 Sub-Protocols
  Each WebSocket sub-protocol defined has a TransportProfileUri defined in OPC 10000-7 . The Client shall request a sub-protocol. If the Server does not support the sub-protocol requested ... Client, the Client shall close the connection and report an error
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  6.5.5 ApplicationRecordDataType
  defines a DataType which represents a record in the GDS . If the ApplicationType is Client, and the Client supports reverse connect then the ServerCapabilities shall include RCP and all DiscoveryUrls ... supported. If the application does not support OPC UA then the ApplicationType is Client and the ServerCapabilities shall be NA. If the ApplicationType is ClientAndServer the ServerCapabilities may include
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.7.1 Overview
  Overview There are a few common workflows that a CertificateManager, as a Client, executes against the ServerConfiguration Object or a BaseApplicationConfiguration Object in the ManagedApplications Folder
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  A.5 Client use of an AliasName Server
  Client use of an AliasName Server AliasNames allow a Client to find TagVariables or Topics easily. Many industrial systems assign tags to specific measurement or sensors. These tags follow established ... this specification does not provide or even suggest any nomenclature. A Client could be configured to display or use the information provided by the sensor TI101, but the actual address/location
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.2.2.9 Reliable update of Devices that are out of reach
  manual reset or replacement, the update shall always result in a working OPC UA Client - Server connection. This requires an additional confirmation by the update Client, so that the Server
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.3.4.5 FileSystem option
  FileSystem based Loading provides an open structure of files and directories where a Client can read and write. These files could be e.g., configuration, setup files or recipes. Note ... expose the current version number(s) of the system. Therefore, a Software Update Client requires additional vendor-specific information, or other companion specifications must define a more specific