OPC UA PubSub Sniffing concepts: Difference between revisions
From OPC Labs Knowledge Base
| Line 11: | Line 11: | ||
(TBD) | (TBD) | ||
== Parsed and unparsed messages == | == Parsed and unparsed messages == | ||
When the message or its part is encrypted, it is possible that the capture mechanism will not be able to decrypt the full message contents, but will still be able to determine the type of the message and some PubSub header information. Such case is indicated by one of the ''unparsed'' capture types. | Normally, the capture mechanism parses all parts of the message that are necessary to collect the information provided by the message. When the message or its part is encrypted, it is possible that the capture mechanism will not be able to decrypt (and parse) the full message contents, but will still be able to determine the type of the message and some PubSub header information. Such case is indicated by one of the ''unparsed'' capture types. | ||
= Capture header = | = Capture header = | ||
Revision as of 07:57, 14 August 2022
Introduction
(TBD)
Capture types
(TBD)
Individual capture types
(TBD)
Capture type groupings
(TBD)
Terminal and non-terminal messages
(TBD)
Parsed and unparsed messages
Normally, the capture mechanism parses all parts of the message that are necessary to collect the information provided by the message. When the message or its part is encrypted, it is possible that the capture mechanism will not be able to decrypt (and parse) the full message contents, but will still be able to determine the type of the message and some PubSub header information. Such case is indicated by one of the unparsed capture types.
Capture header
(TBD)
Special cases
Transport message auto-transformations
(TBD)
Security and sniffing
(TBD)
Data capture with sniffing
(TBD)
