### Summary The GitLab VSCode plugin experiences certificate validation issues in highly controlled/limited enterprise environments due to problems with the certificate trust store configuration. ### Steps to reproduce <!--How one can reproduce the issue - this is very important--> ### What is the current _bug_ behavior? * Plugin fails to establish secure connections in environments with custom certificate authorities * Certificate validation errors prevent proper functionality * Current documentation may not clearly address certificate chain requirements ### What is the expected _correct_ behavior? ### Documentation Updates * Update documentation to clarify downloading the **full certificate chain** rather than individual certificates * Provide clear instructions for enterprise environments with custom CAs * Include troubleshooting steps for certificate trust store issues ### Plugin Enhancement * Update VSCode GitLab Plugin to prompt users to import certificate chain when certificate issues are detected * Implement better error handling and user guidance for certificate-related failures * Add configuration options for custom certificate paths/trust stores ### ### Possible fixes <!--If you can, link to the line of code that might be responsible for the problem--> /cc @tmarsh1 ### References - Customer call https://docs.google.com/document/d/1vhXegoK4Of3o-iA51NlIx7PmtuvEPpANVA0x3wTZHlI/edit?tab=t.0#bookmark=id.flagd35eu1kq