I have defined an application for WTA and some traffic is classified correclty but not all of the traffic.
Some conversations are showing up under https instead of the application for which I have installed the correct key.
SteelCentral Appresponse is not classifying all the traffic for my defined application in WTA (Web Transaction Analysis)
Categories:
Solution Number:
S28743
Last Modified:
2021-06-09
Issue
Solution
Check the trace for the supported algorithms and if you using the correct cipher then check the trace for "Extension: Unknown 23".
It indicates the client is using: "RFC7627 Extended Master Secret Extension"
In the example below the correct cipher suite is supported but the extension is causing the issue:
.png)
Bug 256783 - [AppResponse] -WTA SSL decoding support for Extended Master Secret Extension (RFC7627) was logged for this issue and is resolved in AR11 version 11.9.0 and onwards.
It indicates the client is using: "RFC7627 Extended Master Secret Extension"
In the example below the correct cipher suite is supported but the extension is causing the issue:
Bug 256783 - [AppResponse] -WTA SSL decoding support for Extended Master Secret Extension (RFC7627) was logged for this issue and is resolved in AR11 version 11.9.0 and onwards.
Environment
SteelCentral Appresponse, WTA, Web Transaction Analysis, decryption, AR11, AppTransaction Analyzer
Related Bugs
Bug 256783 - [AppResponse] -WTA SSL decoding support for Extended Master Secret Extension (RFC7627)
Attachments
Related Files
NOTICE: Riverbed® product names have changed. Please refer to the Product List for a complete list of product names.
Can't find an answer? Create a case