Search

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

18 result(s) for Ticket

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

3.1.19 Ticket

Ticket a document that identifies a Device or Composite and has a DigitalSignature
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.1 Device Lifecycle

other actors. During Device Manufacture, Applications may be installed on the Device . A Ticket describing the Device is created and signed by the Manufacturer. Composite Assembly A Composite is created ... Composite Assembly, Applications may be installed on the Devices contained in the Composite . A Ticket describing the Composite is created and signed by the CompositeBuilder. Distribution The Device or Composite
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.2.3 Transfer of Physical Control

control occurs, the supplier ships the equipment (a Device or Composite ) and an electronic Ticket (see 6 ) that describes the equipment. The receiver may use the Ticket to authenticate
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

5.1 Device Identity

ensure these Certificates are verifiable for the expected lifetime of the Device. The Ticket mechanism described in 6 includes the option to extend the validity period by adding Signatures created
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

5.3 Composite Identity

specification. The URI names with the CompositeInstanceUri and ProductInstanceUri are identified by finding a Ticket that contains the values. URI names that cannot be matched to a Ticket are ignored
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.1 Tickets

document that contains information that needs to be provided with a Device . A Ticket is the term used for a document that describes one or more Devices ... chain of physical control. The current owner of a Device validates the Ticket by choosing a Signature created by an authority it trusts. For example, a CompositeBuilder re-signs
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.2 Ticket Distribution

Ticket Distribution When physical control over Devices and/or Composites is transferred from one organization to another there needs to be a physical transfer of goods and an electronic transfer ... network. The ProductInstanceUri and CompositeInstanceUri are used to correlate a Device with a Ticket . A Ticket can be verified before the Devices are connected to the network or done when
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.4 Acquiring and Validating Tickets

Registrar . When a new Device is detected on the network the matching Ticket is found which confirms that the Device is authorized. The second strategy uses a Ticket that ... distributed with the Device or Composite . This Ticket could be stored on the Device or on physical media that was delivered with the Device . When a Device is connected
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

7.1 Overview

steps to determine trust are: Read all DeviceIdentity Certificates from the Device ; Locate a Ticket that has a ProductInstanceUri that matches one or more DeviceIdentity Certificates ; Validate the Ticket ... already been validated (see 6.4 ); Select and Validate DeviceIdentity Certificate that matches the Ticket ; Establish a secure connection to the Device using the selected DeviceIdentity Certificate. Issue a DCA Application
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

7.2 Pull Management

DeviceIdentity Certificates to the Registrar which then attempts to locate a valid Ticket that matches one of the Certificates . If a Composite Ticket that matches the Device ProductInstanceUri exists then ... only DeviceIdentity Certificates with the CompositeInstanceUri are considered by the Registrar . If no Ticket is found the Registrar asks the Device to provide any Tickets that it has by returning
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

7.3 Push Management

returned in EndpointDescriptions returned by GetEndpoints . The Registrar looks for a pre-validated Ticket that matches the Certificate in one of the Endpoints . If none found it chooses ... check its revocation status. If the Registrar finds an EndpointDescription that matches a valid Ticket it will create a new SecureChannel using that EndpointDescription . It provides the DCA Certificate
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 ... document is as follows. { "payload":"BASE64URL(UTF8(JSON encoded Ticket))", "signatures":[ {"protected":"BASE64URL(UTF8(JSON encoded protected header))", "header
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

8.2.2 BaseTicketType

BaseTicketType The BaseTicketType is an abstract base class for a Ticket . The fields of this DataType are defined in Table 7 . Table 7 - BaseTicketType Structure Name Type Description BaseTicketType ... need to validate DeviceIdentity Certificates on the Device that were installed when the Ticket was created. Its representation in the AddressSpace is defined in Table 8 . Table 8 - BaseTicketType Definition
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.3 ProvideIdentities

Certificate that the DCA needs to use to complete the registration process. matchingTicket The Ticket describing the Device which the Registrar accepted. applicationId The identifier assigned by the CertificateManager ... identity Certificates can be verified. Bad_TicketRequired The Device has to provide a Ticket before it can be accepted. Bad_NotFound No valid Ticket was found. Table 18 specifies
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.10 DeviceRegistrarAdminType

manage the Certificates for authorities that sign Tickets . If a Device provides a Ticket, it is accepted automatically if and only if the signing Certificate is in this list ... trusted DeviceIdentity Certificates . This list can contain individual DeviceIdentity Certificates that have a valid Ticket or it can contain the issuers for DeviceIdentity Certificates that are provided out of band
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.11 RegisterTickets

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 ... signed Tickets which should be treated as trusted. results The result of the Ticket validation process described in 6.4 . If validation fails the returned value is Bad_TicketInvalid . Method Result
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.12 UnregisterTickets

Tickets does not affect Devices that were previously accepted using the 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 in the results argument. If a Ticket does not exist the error is Bad_NotFound . This Method shall
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.14 DeviceIdentityAcceptedAuditEventType

Registrar accepts a DeviceIdentity . This occurs when the Registrar finds a matching validated Ticket and is able to validate a DeviceIdentity Certificate . This Event and it subtypes are security related ... HasProperty Variable 2:Certificate 0:ByteString 0:PropertyType Mandatory 0:HasProperty Variable 2:Ticket 0:EncodedTicket 0:PropertyType Mandatory 0:HasProperty Variable 2:Composite 0:EncodedTicket 0:PropertyType Mandatory Conformance