Github Enterprise and HTTPS certs

This is a

• bug report
• feature request

Description

VSCode: 1.28.2 Extension: 2.1.1

I’m using Github Enterprise at the company.

I get this error on trying to dl gists:

GIST ERROR: Could Not Insert > Reason: request to https://github.example.com/api/v3/gists?per_page=9999 failed, reason: unable to verify the first certificate

Our Github Enterprise instance is NOT behind HTTPS proxy. I still set it like this: https://stackoverflow.com/questions/36506539/how-do-i-get-visual-studio-code-to-trust-our-self-signed-proxy-certificate

Predictably, this has not helped.

Unfortunately let’s just say that there is no way to get our GHE to get proper certificates installed.

Obviously, this may be the core VSCode issue and not the one in your extension. If there’s no way to fix this on your side, pls let me know, I’ll open bug report at main VSCode repo.

[mrkafk]

It is so annoying that I cannot access gists that I’ve done some investigation myself.

Octokit seems to provide option for an https agent:

const Octokit = require('@octokit/rest')
const octokit = new Octokit({
  // see "Authentication" section below
  auth: undefined,

  // setting a user agent is required: https://developer.github.com/v3/#user-agent-required
  // v1.2.3 will be current @octokit/rest version
  userAgent: 'octokit/rest.js v1.2.3',

  // add list of previews you’d like to enable globally,
  // see https://developer.github.com/v3/previews/.
  // Example: ['jean-grey-preview', 'symmetra-preview']
  previews: [],

  // set custom URL for on-premise GitHub Enterprise installations
  baseUrl: 'https://api.github.com',

  request: {
    // Node.js only: advanced request options can be passed as http(s) agent,
    // such as custom SSL certificate or proxy settings.
    // See https://nodejs.org/api/http.html#http_class_http_agent
    agent: undefined,

    // request timeout in ms. 0 means no timeout
    timeout: 0
  }
})

Per https://nodejs.org/api/https.html#https_https_globalagent :

The following additional options from tls.connect() are also accepted: ca, cert, ciphers, clientCertEngine, crl, dhparam, ecdhCurve, honorCipherOrder, key, passphrase, pfx, rejectUnauthorized, secureOptions, secureProtocol, servername, sessionIdContext.

So there could be a way of specifying local CA root cert or specific HTTPS cert for this.

If you make a test version of the extension, I’m willing to test it. (never compiled VSCode extension myself so I’m not sure if I can do that correctly, but I can test .vsix file)

[kenhowardpdx]

https://nodejs.org/api/https.html#https_https_request_options_callback