Search

Scope: Core (OPC-10000-*) All specs

17 result(s) for Tickets

OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.2.6 Roles and Privileges

known Roles for Onboarding Name Description RegistrarAdmin The Role grants rights to manage the Tickets known the Registrar and approve Devices when automatic authentication was not possible. SoftwareUpdateAdmin The Role
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.3.1 Distribution

another. This transfer of physical control is accompanied by the electronic transfer of Tickets as described
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.1 Tickets

Tickets The Device lifecycle shown in Figure 1 implies information needs to flow between businesses when there is a transfer of physical control over a Device (see 4.2.3 ). How this ... document have not been altered and that they confirm the origin of the Device . Tickets are long lived documents which means the signing Certificate should be issued by a widely
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.2 Ticket Distribution

needs to be a physical transfer of goods and an electronic transfer of the Tickets associated with the Devices and Composites . The Tickets allow the new user to verify ... Manufacturer and/or CompositeBuilder , however, a trusted intermediary, such as a Distributor , could create the Tickets or add additional Signatures to the existing Tickets . Properly verifying the origin of Devices requires
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.4 Acquiring and Validating Tickets

Acquiring and Validating Tickets Device authentication depends on a process for creating, distributing and validating Tickets which contain information needed to determine if any given Device is allowed ... connected to the OwnerOperator's network. There are two strategies for validating Tickets that depend on how the Tickets are acquired. The recommended approach is to rely
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

7.1 Overview

subjectAltName of the Certificate . The Registrar first searches the set of pre-validated Tickets that were provided out-of-band for a match. If that fails it either calls ... subjectAltName . A Device that is part of a Composite should provide the Composite Tickets in the RequestTickets or ProvideTickets Method. Partial matches to DeviceIdentityTickets in CompositeIdentityTickets are rejected (i.e. Certificates
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

7.2 Pull Management

Registrar . If no Ticket is found the Registrar asks the Device to provide any Tickets that it has by returning a Bad_TicketRequired error. If a valid Ticket is found
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

7.3 Push Management

establishes a SecureChannel and calls RequestTickets . The Registrar needs to validate the Tickets returned by the Device which requires access to the Certificate that created one of the Signatures
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

8.1 Signed Ticket Encoding

Signed Ticket Encoding All Tickets (see 8.2.3 and 8.2.4 ) are encoded as JSON documents. These JSON documents secured with digital signature applied to the general serialization described ... computed on the following byte array: <protected header>.<payload> Tickets may have additional signatures added by any actor in the supply chain. For example, a CompositeBuilder
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

8.2.6 CertificateAuthorityType

Authority (CA) used to issue Certificates to Devices , Composites or to organizations that create Tickets . The fields of this DataType are defined in Table 15 . Table 15 - CertificateAuthorityType Structure Name
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.2 DeviceRegistrarType

manage with the Registrar . The Administration Object allows an administration Client to manage Tickets and Certificates received out of band that are needed for the automated registration process
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.3 ProvideIdentities

SecureChannel . Signature ProvideIdentities ( [in] 0:ByteString [] identities, [in] 0:ByteString [] issuers, [in] 0:EncodedTicket [] tickets, [out] 0:ByteString selectedIdentity, [out] 2:BaseTicketType matchingTicket, [out] 0:NodeId applicationId, [out] 2:ManagerDescription ... Certificates needed to verify the DeviceIdentity Certificates . Certificates that cannot be verified are ignored. tickets The signed Tickets stored on the Device . This argument may be null. If the Registrar
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.10 DeviceRegistrarAdminType

DeviceRegistrarAdminType The DeviceRegistrarAdminType O bjectType that provides an interface to manage the TrustLists and Tickets used by the Registrar when authenticating Devices on a network. The ObjectType is defined ... Registrar Administration The RegisterTickets Method allows an administration Client to provide a list of Tickets for Devices and Composites that it is expecting to install on the network. Any Device
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.11 RegisterTickets

RegisterTickets The RegisterTickets Method allows an administration Client to provide a list of Tickets for Devices and Composites that it is expecting to install on the network. Any Device which ... correlated with one of these Tickets will be accepted automatically. This Method validates each Ticket . Invalid Tickets are rejected. Validation errors are returned in the results output argument. This Method
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.12 UnregisterTickets

UnregisterTickets The UnregisterTickets Method allows a RegistrarAdmin to remove Tickets for Devices and Composites that it previously provided. Removing Tickets does not affect Devices that were previously accepted using ... Tickets . If the Ticket does not exist an error is returned in the results output argument. If an error processing a Ticket occurs the error for that Ticket is returned
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.3.3 ProvisionableDeviceType

IsSingleton is TRUE. The RequestTickets Method allows the Registrar to request the list of Tickets stored on the Device . The SetRegistrarEndpoints Method allows a configuration Client to provide the location
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.3.4 RequestTickets

RequestTickets The RequestTickets Method allows a Client to request the list of Tickets stored on the Device . It is called by a Client using PushManagement to authenticate a Device ... Registrar follows the process described in 7 to select and validate one of the Tickets . Signature RequestTickets ( [out] 0:EncodedTicket [] tickets ); Argument Description tickets The signed Tickets stored