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 126.96.36.199.3 for a complete description of the signing mechanism.
This header layout is basically the same as the header layout defined in A.2.4 but with additional security level ‘signing but no encryption’.
The NetworkMessage header layout with signing is shown in Figure A.2.
Table A.3 – UADP NetworkMessage header layout with integrity (signing)
|ExtendedFlags1||Byte||Bit 4: Security enabled|
|SecurityFlags||Byte||Bit 0: NetworkMessage Signed enabled Bit 1: NetworkMessage Encryption disabled Bit 2: SecurityFooter disabled Bit 3: Force key reset disabledBit range 4-7: Reserved|
|SecurityTokenId||IntegerId||The ID of the security token that identifies the security key in a SecurityGroup.|
|MessageNonce||Byte||A number used exactly once for a given security key.|