As a PRTG User, I want to be able to test the full range of TLS connections, including client certificate protected channels
Details of User Story
if a TLS connection is protected by a client certificate, the server will terminate the TLS-connection if not presented with a proper certificate by the client. IN such a case, the PRTG will "see" the TLS connection, but is unable to check any of it's properties or access the content behind it. (e.g. HTTPS-Server) (see ) Client certificates are used in certain (probably growing) buisness use-cases (see ) but also in a few government related use-cases (e.g. eID card or similar)
- TLS Connection Sensor / TLS Certificate Sensor accepts Client-Certificates
- HTTPS Sensor accepts client-certificates
- all other TLS Sensors accept client certificates This basically gives us a set of cornerstones that need to be there in order for the feature to be implemented.