In all Versions of SystemEDGE SRM monitoring HTTPS sites are available.
With a number of SSL vulnerabilities like poodle, and HeartlBleed, people are moving off SSL authentication of SSLvX (like SSLv3) and moving to a more secure TLS authentication.
In the out of the box versions of SystemEDGE SRM, HTTPS sites will fail because SRM is currently using TLSv1/SSLv3 only as the highest Auth version. This is dependent on the JRE that is used to run the SRM AIM:
JRE 6 will allow TLSv1 and SSLv3
JRE 7/8 will allow TLSv1.2, TLSv1.1, TLSv1, SSLv3.
It is important to note that as the JRE version changes, the in use JRE may remove certain legacy ciphers/protocols and if it does then that will no longer be a supported site.
The following errors may be logged in the jcollector.log when encountering TLSv1.2 sites on an unpatched SRM AIM.
ERROR: jcollector.SATestException: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
[LOG_FATAL][2018-06-12 12:58:57][Thread:Thread-857][Pass #5]: IOException thrown by the html page download: javax.net.ssl.SSLException: Unsupported record version Unknown-0.0
[LOG_CRITICAL][2018-06-12 12:58:57][Thread:Thread-857][Pass #5]: [#12039] ERRSRC:https ERRCODE:58 INDEX:12039 NAME: TESTDESC:[test description] ERROR: jcollector.SATestException: javax.ne.ssl.SSLException: Unsupported record version Unknown-0.0