Is the Broadcom "Data Editor for Mainframe" VS Code Extension V1.1.2 or higher version able to connect to a "File Master Plus Server" using a HTTPS connection if the "File Master Plus Server" presents a self-signed TLS server certificate (and the host name in the returned self-signed TLS server cert does not match the host name of the URL request)?
Does it need to explicitly configure to trust the self-signed TLS server cert and to disable TLS host name validation for the connections from "Data Editor for Mainframe" to the "File Master Plus Server" to make that work?
Windows, Visual Studio Code, Z/OS
To resolve the connection issue, enable the http.systemCertificates option in the VS Code settings.
Once enabled, you will need to install your self-signed certificate into your operating system's trust store.
Installation Steps
For Windows:
1. Double-click your .crt or .pem file.
2. Click Install Certificate...
3. Select Local Machine, then choose Place all certificates in the following store.
4. Select Trusted Root Certification Authorities and finish the wizard.
For macOS:
1. Open the Keychain Access app.
2. Drag and drop your certificate into the System keychain.
3. Double-click the certificate, expand the Trust section, and set "When using this certificate" to Always Trust.
Hostname Verification
Regarding the hostname mismatch: unfortunately, this will still cause a connection error. The hostname in the TLS certificate must match the URL host you are requesting. To bypass this, we would need to update the extension code to include an option for disabling hostname verification.