Search

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

16 result(s) for SecurityHeader

OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

6.7.2.5.1 Encryption other than Authenticated Symmetric Encryption (AEAD)

MessageChunkSize - MessageHeaderSize - SecurityHeaderSize - SignatureSize - 1)/CipherTextBlockSize) - SequenceHeaderSize; The MessageHeaderSize is 12 bytes and the SecurityHeader size depends on whether symmetric or asymmetric cryptography is used. The SequenceHeaderSize is always
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

6.7.4 Establishing a SecureChannel

Server shall verify that a SenderCertificate and a ReceiverCertificateThumbprint were specified in the SecurityHeader
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

6.8.1 Secure Channel Handshake

Initialization Vector Name Bytes Length TokenId 4 The TokenId specified in the SecurityHeader of MessageChunk being processed. It is encoded as a UInt32 as described in 5.2.2.2. LastSequenceNumber
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.4.2 NetworkMessage layout

UADPFlags is false. Bit 3: DataSetClassId enabled Bit 4: SecurityHeader enabled If this flag is enabled, the NetworkMessage header includes the SecurityHeader , otherwise the SecurityHeader is omitted. If the SecurityMode ... FieldMetaData of the DataSetMetaData associated with the DataSetMessage contained in the NetworkMessage . SecurityHeader The security header shall be omitted if bit 4 of the ExtendedFlags1 is false. SecurityFlags Byte
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.4.3.2 AES-CTR

from GetSecurityKeys . MessageNonce Byte [8] The first 8 bytes of the Nonce in the SecurityHeader of the NetworkMessage . For AES-CTR mode the length of the SecurityHeader Nonce shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.6.3 Discovery announcement header

ExtendedFlags2. The actual security settings for the NetworkMessage are indicated by the SecurityHeader . The encoding of the discovery announcement header structure is specified in Table 168 . Table 168 - Discovery announcement
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.6.12.1 General

Publisher as receiver. The actual security settings for the NetworkMessage are indicated by the SecurityHeader
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.4 Header layout for NetworkMessages

PublisherId is of DataType UInt64 Bit 3: DataSetClassId enabled = 0 Bit 4: SecurityHeader enabled = 0 Bit 5: Timestamp enabled = 0 Bit 6: PicoSeconds enabled = 0 Bit 7: ExtendedFlags2 enabled
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.5 Header layout for NetworkMessages with integrity (signing)

integrity (signing) UADP messages may be signed to ensure integrity. In this case the SecurityHeader and the Signature have to be added to the message. See clause ... UADP NetworkMessage header layout with integrity (signing) Name Type Restrictions ExtendedFlags1 Byte Bit 4: SecurityHeader enabled = 1 SecurityHeader SecurityFlags Byte Bit 0: NetworkMessage Signed enabled = 1 Bit 1: NetworkMessage Encryption
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.6 Header layout for NetworkMessages with integrity and confidentiality (signing and encryption)

signing and encryption) UADP messages may be signed and encrypted. In this case the SecurityHeader and the Signature have to be added to the message. See clause ... NetworkMessage header layout with integrity and confidentiality Name Type Restrictions ExtendedFlags1 Byte Bit 4: SecurityHeader enabled = 1 SecurityHeader SecurityFlags Byte Bit 0: NetworkMessage Signed enabled = 1 Bit 1: NetworkMessage Encryption
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.9 Example fixed message layout with integrity

fields and DataSet fields is constant like described in A.2.1.8 . Additional to this the SecurityHeader is activated for signing (but no encryption). Figure A.6 - Example for fixed message layout without
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.4 Header layout for NetworkMessages

PublisherId is of DataType UInt64 Bit 3: DataSetClassId enabled = 0 Bit 4: SecurityHeader enabled = 0 Bit 5: Timestamp enabled = 0 Bit 6: PicoSeconds enabled = 0 Bit 7: ExtendedFlags2 enabled
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.5 Header layout for NetworkMessages with integrity (signing)

UADP NetworkMessage header layout with integrity (signing) Name Type Restrictions ExtendedFlags1 Byte Bit 4: SecurityHeader enabled = 1 SecurityHeader SecurityFlags Byte Bit 0: NetworkMessage Signed enabled = 1 Bit 1: NetworkMessage Encryption
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.6 Header layout for NetworkMessages with integrity and confidentiality (signing and encryption)

signing and encryption) UADP messages may be signed and encrypted. In this case the SecurityHeader and the Signature have to be added to the message. See clause ... NetworkMessage header layout with integrity and confidentiality Name Type Restrictions ExtendedFlags1 Byte Bit 4: SecurityHeader enabled = 1 SecurityHeader SecurityFlags Byte Bit 0: NetworkMessage Signed enabled = 1 Bit 1: NetworkMessage Encryption
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

D.3.2 Header layout for NetworkMessages

PublisherId is of DataType UInt64 Bit 3: DataSetClassId enabled = 1 Bit 4: SecurityHeader enabled configurable (default=1) Bit 5: Timestamp enabled = 0 Bit 6: PicoSeconds enabled = 0 Bit 7: ExtendedFlags2
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

D.3.3 Header layout for NetworkMessages with integrity (signing)

UADP NetworkMessage header layout with integrity (signing) Name Type Restrictions ExtendedFlags1 Byte Bit 4: SecurityHeader enabled = 1 SecurityHeader SecurityFlags Byte Bit 0: NetworkMessage Signed enabled = 1 Bit 1: NetworkMessage Encryption