Search

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

12 result(s) for Certificate Authority

OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

3.1.16 Certificate Authority

Certificate Authority entity that can issue Certificate s, also known as a CA Note 1 to entry: The Certificate certifies the ownership of a Public Key by the named subject
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

9.1 Overview

with X.509 v3 Certificate that is the ApplicationInstanceCertificate ) or can be signed by a Certificate Authority (The signature is generated by the Private Key associated the X.509 v3 Certificate
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

9.4.2 Certificate management for developers

SecureChannel . It can be used to determine access rights and to track activities (auditing). Certificate Authority (CA) - A Certificate Authority (CA) is an administrator or organization which is responsible ... creating and managing Certificates (it is usually a partially automated software product). The Certificate Authority verifies that Claims placed in the ApplicationInstanceCertificate is correct and adds a Digital Signature
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

6.1.2 Obtaining and installing an ApplicationInstanceCertificate

application instance; The validFrom and validTo date for the Certificate . ApplicationInstanceCertificates issued by a Certificate Authority (CA) shall contain the following additional information: The name of the Certificate Authority that ... issued the Certificate ; The public key issued to the application by the Certificate Authority ; A digital signature created by the Certificate Authority . Note Self-signed Certificates contain this information
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

6.1.5 Creating a Session

Establishing a Session Figure 22 illustrates the interactions between a Client , a Server , a Certificate Authority (CA) and an identity provider. The CA is responsible for issuing the ApplicationInstanceCertificates ... identity provider depends on the user identity token. It could be a Certificate Authority , an Authorization Service or a proprietary database of some sort. The Client and Server shall prove
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.3 ApplicationInstanceCertificate

Table 110 - ApplicationInstanceCertificate Name Type Description ApplicationInstanceCertificate structure ApplicationInstanceCertificate with signature created by a Certificate Authority . version String An identifier for the version of the Certificate encoding. serialNumber ByteString
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

3.1.3 CertificateRequest

CertificateRequest a PKCS #10 encoded structure used to request a new Certificate from a Certificate Authority . Note 1 to entry: Devices have hardware-based mechanisms, such
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

5.1 Device Identity

this implies the other organization is trusted as an authority capable of assuring the origin of the Device . The LDevID Certificate may use the same keypair as the IDevID Certificate ... GeneralizedTime value 99991231235959Z in the notAfter field). The Manufacturer is responsible for creating the Certificate Authority used to issue the Certificates. Properly verifying the Certificates requires that the CA Certificate
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.1 Tickets

documents which means the signing Certificate should be issued by a widely trusted root Certificate Authority that is likely to be in business even if the Manufacturer or CompositeBuilder ... owner of a Device validates the Ticket by choosing a Signature created by an authority it trusts. For example, a CompositeBuilder re-signs the Tickets for the Devices to associate
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.4 Acquiring and Validating Tickets

Ticket signing Certificate with the Registrar or if the issuer is a trusted root CertificateAuthority . The latter criteria is only allowed if the Ticket was provided out of band ... example, companies that provide C ertificates for code/document signing could be a root CertificateAuthority for Ticket signing. Each OwnerOperator is responsible for maintaining a list of trusted root CertificateAuthorities which
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

7.1 Overview

found a valid Ticket that matches a DeviceIdentity Certificate , it can use the CertificateAuthority in the Ticket to validate the selected Certificate using the process described
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

8.2.6 CertificateAuthorityType

CertificateAuthorityType The CertificateAuthorityType describes a Certificate Authority (CA) used to issue Certificates to Devices , Composites or to organizations that create Tickets . The fields of this DataType are defined in Table ... Structure DataType defined in OPC 10000-5 . authorityCertificate 0:ByteString The DER encoded Certificate used to issue Certificates. issuerCertificates 0:ByteString [] The DER encoded form of the Issuer