Search

11 result(s) for Signatures

• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  9.1 Overview
  provide the same level of security and can be used in Asymmetric Cryptography. The Signatures can be generated using a variety of algorithms, where the algorithms provide different levels
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.1.8 Calculating Signatures used in CreateSession and ActivateSession
  Calculating Signatures used in CreateSession and ActivateSession There are a number of Signatures which Client and Server applications may need to calculate when calling CreateSession and ActivateSession . The new Signature ... calculation algorithm, called channel bound Signatures , requires that the Certificates used to establish the SecureChannel be used in the calculation. Certificates that are passed as parameters in CreateSession are used
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.1 Security Handshake and Security Policies
  encryption is implied by the SymmetricEncryptionAlgorithm . The length of the keys used for creating Signatures is specified by the DerivedSignatureKeyLength . The MinAsymmetricKeyLength and MaxAsymmetricKeyLength are constraints that apply ... security enhancements are required for all applications that support the SecurityPolicy . Channel-bound signatures are described in OPC 10000-4 and updates to key derivation on renew are described
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  5.1 Device Identity
  mechanism described in 6 includes the option to extend the validity period by adding Signatures created by trusted Certificate Authorities that have not expired
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  6.1 Tickets
  even if the Manufacturer or CompositeBuilder has gone out of business. Tickets allow additional Signatures to be added at any time by an entity in the chain of physical control
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  6.2 Ticket Distribution
  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 that OwnerOperators and other downstream
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  6.4 Acquiring and Validating Tickets
  valid; Tickets that are not valid shall not be used. Tickets may have multiple signatures added by different actors in the supply chain. The Registrar only needs to find ... supply chain only add a Signature if at least one of the existing Signatures is valid and created by an authority the actor trusts. Registrars shall not trust authorities unless
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  7.3 Push Management
  Device which requires access to the Certificate that created one of the Signatures and the ability to check its revocation status. If the Registrar finds an EndpointDescription that matches
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  7.4.2.1 Overview
  Device moves through the supply chain. The FDO Ownership Voucher has multiple Signatures provided by each intermediary in the supply chain. However, the FDO Device only knows the first PublicKey
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  8.1 Signed Ticket Encoding
  follows. { "payload":"BASE64URL(UTF8(JSON encoded Ticket))", "signatures":[ {"protected":"BASE64URL(UTF8(JSON encoded protected header))", "header": JSON encoded ... following byte array: <protected header>.<payload> Tickets may have additional signatures added by any actor in the supply chain. For example, a CompositeBuilder shall add Signatures
• OPC-30020 – MDIS OPC UA Companion Specification
  6.14.3 MDISInformationObjectType Definition
  BaseObjectType (see OPC 10000-5 ) 0:HasComponent Object TimeSynchronization MDISTimeSyncObjectType O 0:HasComponent Object Signatures 0:FolderType O 0:HasComponent Variable MDISVersion MDISVersionDataType MDISVersionVariableType M, RO ConformanceUnits MDIS Information version ... provide time information to a Server if required. See 6.1.16 for additional details. Signatures is a folder that contains all of the currently available signatures (profiles). The individual signature