Authentication SSL Cert Error when connecting to Hosted JIRA

[Timothy Beamish]

Our company hosts Jira at:
https://jira.company.local

We have a SSL cert tied to that domain but since it’s a “.local” domain we have to use a self-signed cert, thus it isn’t strictly valid and when we view the site in a browser, we always get a warning and have to manually accept the cert to proceed. This, of course, causes a problem when extensions such as this one attempt to access that domain - the extension also sees the self-signed cert and issues the error:

Authentication error
Error authenticating with Jira: Error: unable to verify the first certificate

I realise we should sort out our own certificate verification problems but it’s a nice-to-have feature if this extension would allow us to proceed even when the SSL cert doesn’t verify properly, much like browsers do.

[Jonathan Doklovic]

@Timothy Beamish We’ve just released version 2.0.1 which includes experimental support for self-signed certs.

To test it out you’ll need to do the following:

1. Update to version 2.0.1
2. download your self-signed cert somewhere handy on your filesystem and note the path
3. open up VS Code and use the command palette to open “Preferences: Open Settings (UI)”
4. Search for “SSL”
5. find Atlascode: Custom SSLCert Paths and enter the full absolute path to the cert you downloaded
6. find Atlascode: Enable Custom SSLCerts and make sure the checkbox is checked
7. Try to authenticate again

Please let me know how this goes. If it causes issues or doesn’t work, you can simply uncheck the Enable Custom SSLCerts to turn it off

‌

[Timothy Beamish]

It works!

Thanks so much. I am able to connect to both our self-signed-cert-hosted Jira and Bitbuckets servers.

[Jonathan Doklovic]

Awesome! Glad it’s finally working for you.

[Timothy Beamish]

Oh man, you’ve opened the flood gates of awesome. Brace yourselves for an onslaught of upcoming feature requests.

This plugin is amazing!

[Jonathan Doklovic]

Cheers!

[Jonathan Doklovic]

@Timothy Beamish Heads up, we’re removing the experimental settings for custom certificates and making them part of the settings when you authenticate with a custom site.

This means you’ll need to remove the site you’ve authenticated with and re-authenticate using the new options in the authentication box.

I’ve create a new version you can test this with. You’ll need to install it manually using the “Install From vsix…” option in the extension panel.

Please let me know how it goes!

https://bitbucket.org/atlassianlabs/atlascode/downloads/atlascode-2.0.5-mtls.vsix

[Jonathan Doklovic]

@Timothy Beamish FYI, we’ve released version 2.1.0 which includes the changes mentioned above.

[pook developer]

How I download the SSL certificate? I want to use Bitbucket in VSCODE to make PR, Thanks

[Jonathan Doklovic]

@pook developer You only need an SSL certificate if you’re using Bitbucket server and your company uses a custom and/or a self-signed cert. If that’s the case, you’ll need to talk to your IT department or your Bitbucket admin to get the certificate.