Self-signed certificates for Jupyter URI (Support Jupyter Hub)

Environment data

• VS Code version: 1.32.1
• Extension version (available under the Extensions sidebar): 2019.2.5558
• OS and version: OS X 10.13.6
• Python version: 3.7
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): pipenv, virtualenv
• Relevant/affected Python packages and their versions: Jupyter

Jupyter

Connecting to a Jupyter server via https with a self-signed certificate fails:

Failed to connect to remote Jupyter notebook. Check that the Jupyter Server URI setting has a valid running server specified. 

TypeError: request to https://blah.blah.blah.com:8000/api/contents/?xxxxxxx failed

reason: self signed certificate

Setting:

{
"http.proxyStrictSSL": false
}

has no impact.

[IanMatthewHuff]

Since I promised an update. The workaround is looking good. As long as you trust me that this is the same server name blacked out here is the interactive window hitting a self cert server and connecting and running code. I need to so some more verification that my workaround isn’t exposing any new issues, so I don’t see the fix getting in today. But provided that I don’t fine any blocking issues with the workaround should be early next week. My current plan is to expose some type of allow self signed certs setting that defaults to no as default but can be flipped to true.

[IanMatthewHuff]

Hey Everyone. Sorry about the radio silence here for a while. Currently the @jupyterlab/services that we use to connect to Jupyter servers really only support token authentication and don’t support self signed certificates by default. Recently I’ve worked on a bit of a workaround to get passwords working for with @jupyterlab/services, and I think that I can apply the same workaround to self signed certs. Looking into that as we speak. I should know by tomorrow EOD if this fix will work as well to enable self-certs.