Search
10 result(s) for subjectAltName
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model4.2 URIsautomatically created by the application software. An ApplicationInstance Certificate has the ApplicationUri in the subjectAltName (see OPC 10000-6 ); ProductInstanceUris identify a Device and are assigned by the Device Manufacturer ... DeviceIdentity Certificate has the ProductInstanceUri in the subjectAltName . These URIs conform to RFC 3986 , however, this specification is very open ended. This clause provides recommendations for constructing these URIs
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappingsattributes may be specified. The subject field is completely described in IETF RFC 5280 . subjectAltName applicationUri, hostnames The alternate names for the application instance. Shall include a uniformResourceIdentifier which ... Instance runs. Additional dNSNames may be specified if the machine has multiple names. The subjectAltName field is completely described in IETF RFC 5280 . publicKey publicKey The public key associated with
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings7.5.3 SecurityCertificate as the TLS Certificate provided the correct domain is specified in the subjectAltName field. A Client may use its Certificate as the TLS Certificate and Servers shall accept those
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services7.9.3 StartSigningRequestthen it shall include all fields required by OPC 10000-6 such as the subjectAltName . RequestId The NodeId that represents the request. This value is passed to FinishRequest . The call ... CertificateGroupId parameter. The CertificateRequest parameter is a DER encoded CertificateRequest. The subject, subjectAltName and Public Key are copied into the new Certificate. If the CertificateTypeId is a subtype of ApplicationCertificateType
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services7.10.10 CreateSigningRequestthen it shall include all fields required by OPC 10000-6 such as the subjectAltName . Method Result Codes (defined in Call Service) Result Code Description Bad_InvalidArgument One or more
-
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding3.1.2 ApplicationUriDevice . Note 3 to entry: The Application Instance Certificate has the ApplicationUri in the subjectAltName field
-
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding3.1.10 DeviceIdentity CertificateDevice . Note 1 to entry: All DeviceIdentity Certificates have the ProductInstanceUri as a subjectAltName . Note 2 to entry: All DeviceIdentity Certificates are IDevID or LDevID Certificates as defined
-
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding5.1 Device IdentityCertificate . IDevID Certificate should have the ProductInstanceUri (see 5.2 ) as a uniformResourceIdentifier in the subjectAltName field (see RFC 5280 ). If the IDevID Certificate does not have the ProductInstanceUri the Device ... shall have an LDevID (Locally Significant Device Identifier) Certificate with the ProductInstanceUri in the subjectAltName . If an LDevID Certificate is used it should be installed by the Manufacturer and signed
-
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboardingsame CompositeInstanceUri . The CompositeInstanceUri follows the same rules as ProductInstanceUri (see 5.2 ). The subjectAltName is an array of alternate names for the Device . Each entry in the subjectAltName ... contained by another Composite, then only the outermost CompositeInstanceUri is present. Note that the subjectAltName is a generic field that contains names used for purposes outside the scope of this
-
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding7.1 Overviewfirst looks for a Certificate that has a ProductInstanceUri as a value in the subjectAltName of the Certificate . The Registrar first searches the set of pre-validated Tickets that were ... Certificate that has both the CompositeInstanceUri and the ProductInstanceUri as values in the subjectAltName . A Device that is part of a Composite should provide the Composite Tickets in the RequestTickets