EQAVS1007E - self signed certificate in certificate chain

[heymchri]

This appears related to issues #51 and #52 .
V7R5 with PTFs for Debug Service 3.0.2 installed.

When setting up the trust store with an internal cert, setting an SEP fails with "EQAVS1007E USALID08.INFOR.COM on port 8005 could not be connected. Message received: self signed certificate in certificate chain"

Debug Console shows:
To client: {"seq":0,"type":"event","event":"output","body":{"category":"stderr","output":"Connection settings: { 'host': 'USALID08.INFOR.COM', 'port': 8005, 'secure': true, 'capath': 'undefined', 'ignoreCertificateErrors': false, 'TLS_Version': TLSv1.2 }"}}
Connection settings: { 'host': 'USALID08.INFOR.COM', 'port': 8005, 'secure': true, 'capath': 'undefined', 'ignoreCertificateErrors': false, 'TLS_Version': TLSv1.2 }EQAVS1007E USALID08.INFOR.COM on port 8005 could not be connected.
Message received: self signed certificate in certificate chain
To client: {"seq":0,"type":"event","event":"output","body":{"category":"stderr","output":"EQAVS1007E USALID08.INFOR.COM on port 8005 could not be connected.\nMessage received: self signed certificate in certificate chain\n"}}
EQAVS1007E USALID08.INFOR.COM on port 8005 could not be connected.
Message received: self signed certificate in certificate chain
To client: {"seq":0,"type":"response","request_seq":2,"command":"launch","success":false,"message":"EQAVS1007E USALID08.INFOR.COM on port 8005 could not be connected.\nMessage received: self signed certificate in certificate chain","body":{"error":{"id":9999,"format":"EQAVS1007E USALID08.INFOR.COM on port 8005 could not be connected.\nMessage received: self signed certificate in certificate chain","showUser":true}}}

When setting up the trust store with a cert signed by an external CA (Sectigo), this works just fine.

This issue (or similar ones with the same error message) has been plaguing us for over a year on multiple partitions. On some partitions, we have no issue at all with internal certs, while on others, we occasionally run into the above issue. Also, even when the above error is thrown, sometimes (i.e., not always) just existing and restarting VS Code and reconnecting to the partition gets us past the error.