Search

6 result(s) for Client.

• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.13 OPC UA security related Services
  that are used for applying various security mechanisms to communication between OPC UA Client s and Server s. OPC 10000-4 provides an overview of security in the "Service ... Service Set (specified in OPC 10000-4 ) defines services used by an OPC UA Client to obtain information about the security policies (see 4.6 ) and the Certificate s of specific
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.1.10 Rogue Server or Publisher
  Publisher See 4.3.10 and 4.3.11 for a description of this threat. OPC UA Client applications counter the use of rogue Servers by validating Server ApplicationInstanceCertificates . There would still ... Server would never be able to read and misuse secured data sent by a Client . Also, without the Private Key the Server would never be able to sign a response
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.31 RegisteredServer
  type of application. The enumeration values are defined in Table 109 . The value "CLIENT" (The application is a Client) is not allowed. The Service result shall ... Discovery Server shall check that this file exists before returning the ApplicationDescription to the Client . If the Server did not register with a semaphoreFilePath (it is null or empty) then
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.5.3.2 Authorization Code
  code flow is available to Clients which allow interaction with a human user. The Client application displays a window with a web browser which sends an HTTP ... Service. The Authorization Service validates the code and returns an Access Token to the Client. The complete flow is described in IETF RFC 6749 , 4.1. A requestType of "authorization
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  3.1.10 TimeDomain
  handle out-of-bounds timestamps gracefully, and return the proper StatusCodes to the Client
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  B.3.5 Update sequence using File System based Loading
  device. So, the Resume activity described in Figure 39 cannot be commanded by a Client. In the first steps the device identity and the kind of supported Server options