Authentication error with 2.0.0-beta1

Issue #196 resolved
Archie Henderson created an issue

I’ve just tried logging into my company’s Jira and Bitbucket servers using the new 2.0.0-beta1. I received the authentication error ‘Error authenticating with Jira: Error: unable to verify the first certificate’. This is with version 1.38.0 of VS Code running on Windows 10.

Comments (7)

  1. Jonathan Doklovic Account Deactivated

    @Archie Henderson Does you company use a self-signed SSL certificate?

  2. Archie Henderson reporter

    I didn’t notice you’ve added beta support for this. I’ve now managed to get apply a custom certificate and can successfully authenticate both Jira and Bitbucket. Having a couple of issues with Bitbucket reporting that I appear to have gone offline, but unsure if that’s related.

  3. Jonathan Doklovic Account Deactivated

    @Archie Henderson Thanks for letting us know. The offline message may happen periodically due to network detection but if your connection is reasonably stable, it should go into online mode again in a few seconds. If not, please open another issue for it.

  4. Jonathan Doklovic Account Deactivated

    @Archie Henderson 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

  5. Archie Henderson reporter

    @{557057:3695b794-cde3-43a2-99aa-c0fc6151b754} I’ve tested version 2.0.5 and it works as far as successfully authenticating. Thanks! Am still seeing ‘looks like you’ve gone offline' in various scenarios and I’m sure the network is good. Will open an issue

  6. Log in to comment