TLS Module report empty even though multiple versions of TLS supported

[duncangreene]

Describe the bug
Testrun reports TLS 1.2 and TLS 1.3 are available on the below device (albeit with a "certificate is invalid" description).

The Services Module shows at least 3 services that support TLS (443, 4911 and 5011), although I understand that you don't intend to support TLS tests for non-HTTP services at present.

However the TLS Module section of the report states "no TLS certificates found".

For the avoidance of doubt, the device does present a certificate on 443.

To Reproduce
Steps to reproduce the behaviour:

1. Run test against device offering TLS 1.2 and TLS 1.3.

Expected behaviour
The TLS Module would contain details against TLS 1.2 and/or against TLS 1.3 and/or just the certificate details irrespective of which version of TLS the cert was presented using (assuming exact same cert is presented via both 1.2 and 1.3).

Error logs

jace8000.zip

Environment (please provide the following information about your setup):

• Version: 2.1

Additional context
Only modifications from official 2.1 release are as below.

• resources/test_packs/qualification.json (Set tests to excluded/recommended/informational as appropriate)
• resources/devices/device_profile.json (Add custom questions)

[jhughesbiot]

I tested on a JACE8000 on multiple runs and I was not able to recreate this issue. The only thing I could find that was different was that the server certificate exchange is not captured in the tls module in the provided files that I do see in my attempts.

Can you confirm the station and web service for your JACE are fully booted up in the 5 minute monitor window? It might be possible the web service isn't fully ready when being connected to and not reporting certificates correctly but later when nmap runs, things are more stable.