1. Atlassian Labs Avatar Atlassian Labs
  2. Partner Integrations
  3. atlascode
  4. Issues

Ability to authenticate with hosted servers

Issue #5 resolved
Timothy Beamish created an issue

We host our own JIRA and BitBucket/Stash instances on our intranet. They're invisible to the outside world but do have their own API, etc.

I cannot get this plugin to connect because it defaults to connecting to the public Atlasian servers. If we could configure what URL it wants to connect to, it might solve this issue.

Official response

  •  Nick Rundquist

    Update 2019-10-03

    Version 2.0.0 is now available on the VS Code Marketplace.

    Update 2019-10-01

    Version 2.0.0-beta3 is now available at https://bitbucket.org/atlassianlabs/atlascode/downloads/atlascode-2.0.0-beta3.vsix

    Improvements

    • Added support for merge commit messages

    Bugs fixed

    • Username was not slugified when making calls during Bitbucket server auth flow
    • Sometimes webviews would not load data

    Update 2019-09-27

    Version 2.0.0-beta2 is now available at https://bitbucket.org/atlassianlabs/atlascode/downloads/atlascode-2.0.0-beta2.vsix

    Improvements

    • Added a refresh button on Jira issue view

    Bugs fixed

    • Transitions are now reloaded when an issue is transitioned to get any new available options
    • Fixed bad default JQL in settings.json
    • Fixed error when checking for an empty user object
    • Fixed issue with credentials not saving for all sites

    Original Announcement

    Hello!

    Today we’re excited to announce the availability of version 2.0.0-beta1 for testing.

    This version adds support for Server/Data Center deployments of both Jira and Bitbucket.

    We’re providing this for testing and hope we can get some early feedback. As such, we will not be publishing this version to the VS Code Marketplace, so you’ll need to install this manually:

    Install Instructions:

    1. Download the beta version here: https://bitbucket.org/atlassianlabs/atlascode/downloads/atlascode-2.0.0-beta3.vsix
    2. Within VS Code, click the “Extensions” icon in the App Bar
    3. Using the “…” menu in the upper right of the extensions explorer, choose “Install from VSIX…”
    4. Find the .vsix file you downloaded in step 1 and choose it for installation
    5. After the install is complete you must restart vscode.

    This is a beta version, and there’ll definitely be some bugs. If you find one, create a new issue in this issue tracker.

    If you just want to give us some general feedback, use the in-app feedback form located in the Atlassian Settings page.

    So what else is new?

    New Features:

    • Support for a wider range of Jira features and configurations

      • Time tracking
      • Adding sprints to issues
      • Not having a resolution field
      • And more!

    • View JQL from multiple sites at once in Jira explorer

    • Notifications can be managed and disabled for individual JQL queries

    Enhancements:

    • Pull request comments are now collapsible
    • Selected code will now be included in description when creating issue from a TODO
    • Get the latest information by refreshing any open view
    • Improved performance when creating pull requests or starting work on issues
    • Edit the prepopulated branch name when starting work on an issue
    • User picker for mentions now prepopulated when creating pull requests and Bitbucket issues
    • Edit and delete comments on pull requests

    • Improved settings:

      • Jira and Bitbucket now have their own sections in the settings
      • Jira or Bitbucket features can now be completely disabled
      • Settings can now be saved at either the user level or the workspace level

    Bugfixes:

    • Build statuses now link to the tool that created them
    • Fixed URL creation on Windows
    • TODO triggers no longer require a trailing space
    • Subtasks now report the correct status
    • Pipelines builds triggered manually or by tag creation now show up in the pipelines sidebar

    Thanks!

Comments (122)

  1. Pramod Busam Account Deactivated

    @tbeamish This extension only supports the cloud versions of Jira and Bitbucket currently.

  2. Jack Koppa

    Thanks for the prompt response. Definitely a huge +1 from me for support for self-hosted instances.

    Even though we can't use it at this point, wanted to thank the team for your work on this. Especially this level of customer service: https://twitter.com/tc_saas/status/1100739145566167040

    Presumably, this is going to be a fantastic productivity booster for people on Cloud versions, and please let me know if there's anything we can do to help with or test the enterprise integration.

  3. Jean-Christophe Gay

    Also a huge +1 from me for the support of self-hosted instances. Let me know if there's anything we can do to help with or test the enterprise integration.

  10. GM Murugan

    all we need is an option to customize the auth URL's to on premise hosted atlassian bitbucket server

  18. Rhys Scheuner Account Deactivated

    + 1 please!

    We host our own Jira but use cloud Bitbucket. Would love to have Jira ticket integration!

  28. Chris Wetterman

    Unfortunately I uninstalled this extension as soon as I installed it since it doesn’t support self-hosted instances 😕

  31. Manuel Martini

    Can you stop writing not useful messages like “+1“ or “it does not support self hosted“ please? The bug status is “on hold“ and this should be enough, because that means someone is already working on it, so be patient and wait for Atlassian’s team to implement this properly.

    I just voted this issue with the proper link and I am also watching it, but receiving boring notifications is a bit annoying.

  32. Mark Ewer

    I agree. This doesn’t do me any good at all if it can’t connect to my Jira or Stash servers. It would be nice to have this option since you dropped support for the Visual Studio extension…

  34. Smok Wawelski

    @Manuel Martini “on hold” actually means they see the problem but are NOT working on it at the moment:)

  35. fraunos

    Github has Reactions button, which gives a way to +1 without notifying everyone, which is helpful to see how many people are interested. Writing this just to also bump the issue, because we use self hosted too 😅 Sorry, there’s just no other way to give more attention.

  36. Jeppe Vennekilde

    @fraunos You can vote for issues in the top right of the issue. Same location as where you can follow it.

    This issue currently has 109 votes, followed by the second most popular issue, with only 26, so i assume they are aware of the popularity of the issue

    PS: Sorry to all the people watching this issue and got an email due to this comment 😛

  37. Andreas Frank

    @Jeppe Vennekilde Looking closely, it seems that even the second-, third-, fourth- and fifth-most popular issues are actually very similar to this one if not exactly the same issue…

  45. Daniel Bernard

    I’m driving a change at our company to migrate from ClearCase/ClearQuest UCM to Atlassian Bitbucket/Jira, where we’re using self-hosted Server versions.

    For the teams that are less CLI-minded, GUI-based integrations for Jira/Bitbucket would be a game-changer in being able to sell this as a practical and feature-complete solution.

  57. Ignacio Urruty

    Hi,

    Is it possible to know if this will be addressed in a near future? or we should create our own extension?

    If this will be on hold for 1 year, maybe is better to start doing another extension… 😕

  60. Leandro GUIDA

    We are a non-profit using an on premises Jira instance (Thanks for making this available for non-profit bt the way) and would be amazing to have this working. 🙂

  69. Julius Spudvilas Account Deactivated

    +1 here too.. no use without it unfortunatelly… none of the 10+ projects i work on have the Cloud hosted Jira or Bitbocket instances

  77. Smok Wawelski

    Yes…

    260 votes and absolutely no reaction from developers.

    Only “this is for public cloud” and status “on hold”

    It would be nice to know if there are any plans to do it, or some explanation why it can’t be done (if it can’t be done).

    As others stated before - for many people this extension is now useless as most companies uses local JIRAs not cloud.

  78. Daniel C

    @Alastair Wilkes or @Jonathan Doklovic does any of you know if this issue/feature is going to be solved? I’ve been subscribed to this thread since 2019-04-30. Would you mind at least to answer to people saying that you are investigating this or at least a prevision if this is ever going to be done.

  79. Tsvetan Blagoev Account Deactivated

    +1 for on-prem installs, It’s a feature we would love here at VMware.

  82. Jon Dewitt

    Any updates on what is the most requested issue on the entire project? If this never has a chance of becoming a reality I’d rather just not watch the topic and never use the plugin.

  89. Nick Rundquist

    Update 2019-10-03

    Version 2.0.0 is now available on the VS Code Marketplace.

    Update 2019-10-01

    Version 2.0.0-beta3 is now available at https://bitbucket.org/atlassianlabs/atlascode/downloads/atlascode-2.0.0-beta3.vsix

    Improvements

    • Added support for merge commit messages

    Bugs fixed

    • Username was not slugified when making calls during Bitbucket server auth flow
    • Sometimes webviews would not load data

    Update 2019-09-27

    Version 2.0.0-beta2 is now available at https://bitbucket.org/atlassianlabs/atlascode/downloads/atlascode-2.0.0-beta2.vsix

    Improvements

    • Added a refresh button on Jira issue view

    Bugs fixed

    • Transitions are now reloaded when an issue is transitioned to get any new available options
    • Fixed bad default JQL in settings.json
    • Fixed error when checking for an empty user object
    • Fixed issue with credentials not saving for all sites

    Original Announcement

    Hello!

    Today we’re excited to announce the availability of version 2.0.0-beta1 for testing.

    This version adds support for Server/Data Center deployments of both Jira and Bitbucket.

    We’re providing this for testing and hope we can get some early feedback. As such, we will not be publishing this version to the VS Code Marketplace, so you’ll need to install this manually:

    Install Instructions:

    1. Download the beta version here: https://bitbucket.org/atlassianlabs/atlascode/downloads/atlascode-2.0.0-beta3.vsix
    2. Within VS Code, click the “Extensions” icon in the App Bar
    3. Using the “…” menu in the upper right of the extensions explorer, choose “Install from VSIX…”
    4. Find the .vsix file you downloaded in step 1 and choose it for installation
    5. After the install is complete you must restart vscode.

    This is a beta version, and there’ll definitely be some bugs. If you find one, create a new issue in this issue tracker.

    If you just want to give us some general feedback, use the in-app feedback form located in the Atlassian Settings page.

    So what else is new?

    New Features:

    • Support for a wider range of Jira features and configurations

      • Time tracking
      • Adding sprints to issues
      • Not having a resolution field
      • And more!

    • View JQL from multiple sites at once in Jira explorer

    • Notifications can be managed and disabled for individual JQL queries

    Enhancements:

    • Pull request comments are now collapsible
    • Selected code will now be included in description when creating issue from a TODO
    • Get the latest information by refreshing any open view
    • Improved performance when creating pull requests or starting work on issues
    • Edit the prepopulated branch name when starting work on an issue
    • User picker for mentions now prepopulated when creating pull requests and Bitbucket issues
    • Edit and delete comments on pull requests

    • Improved settings:

      • Jira and Bitbucket now have their own sections in the settings
      • Jira or Bitbucket features can now be completely disabled
      • Settings can now be saved at either the user level or the workspace level

    Bugfixes:

    • Build statuses now link to the tool that created them
    • Fixed URL creation on Windows
    • TODO triggers no longer require a trailing space
    • Subtasks now report the correct status
    • Pipelines builds triggered manually or by tag creation now show up in the pipelines sidebar

    Thanks!

  90. Jesus Martinez Fernandez

    Thanks a lot for this beta but sadly I’m still not able to log in with my custom domain. My company uses our Google account with Two-Factor Authentication to connect to our custom Jira site and if I try to enter my Google credentials it does not work (Error authenticating with Jira: Error: Request failed with status code 401).

    Wouldn’t it be possible to open a browser screen to log in and then redirect to the Atlassian for VSCode plugin similar to what you did when log in to Jira Cloud? Thanks!

    ‌

  91. Gordon Tyler

    After configuring authentication for Bitbucket (personal access token) and then Jira (user password), I encountered a few issues:

    • Clicking the Jira button at the bottom loads the Atlassian Settings page but it goes blank immediately after loading. Similarly when clicking the settings icon in the Jira Issues explorer.
    • In the Jira Issues explorer, clicking the "Configure JQL entries in settings...." item displayed a popup error in the bottom right corner: Ua.config.jira.jqlList.filter is not a function
    • If the Atlassian Settings page has been opened to the Bitbucket settings and then the Jira tab is clicked, the page goes blank.

    Basically, the Jira functionality is unusable right now.

  94. Ignacio Urruty

    Hi I tried to install it.

    But none of the commands are working. I saw that there are some issues about this.. and they did a restart..
    But in my case is not working.. I don’t have direct access to the internet in the computer I tested.
    Vscode Version:

    Version: 1.38.1
    Commit: b37e54c98e1a74ba89e03073e5a3761284e3ffb0
    Date: 2019-09-11T13:30:08.229Z
    Electron: 4.2.10
    Chrome: 69.0.3497.128
    Node.js: 10.11.0
    V8: 6.9.427.31-electron.0
    OS: Linux x64 3.10.0-693.2.2.el7.x86_64

    I’m getting a warning while installing but the next thing is that was installed successfully..
    [2019-09-27 16:38:06.075] [sharedprocess] [warning] Cannot install dependencies of extension: atlassian.atlascode

    [2019-09-27 16:38:06.076] [sharedprocess] [info] Successfully installed the extension: atlassian.atlascode

    Then I close and re open vscode.. and try to run the open settings command.
    My json settings are empty.

    I’m testing in a new clean vscode.

  95. Jonathan Doklovic Account Deactivated

    Ignacio Urruty,

    The extension has some dependencies that VS Code needs to fetch during install. Also, once installed, the extension relies heavily on an internet connection and will not be usable if it can’t reach the public internet.

    ‌

  96. Fredrik Averpil

    I tried logging in with our internal server after having installed the vscode extension;

    Error authenticating with Bitbucket: Error: Request failed with status code 400

    ‌

  97. Jesus Martinez Fernandez

    @{557058:a30b5736-f3cf-41d7-aad0-99c9ffac78ce} thanks for your suggestion but I’m still getting an authentication error even if I set a Google App Password (this time the status code is 403).

    My guessing is that unless I can specify somehow in the Authentication settings that when I use a custom Jira site I want to authenticate with Google, my credentials will be checked in your database (where they’re not stored) and I won’t be able to log in, that’s why I suggested opening a browser window to log in like:

    ‌

  99. Erik Hess

    Thanks for sharing the beta release! Its well on its way to giving us poor hosted users access to a very useful tool. 🙂

    I ran into a problem with my company’s particular implementation, leading to a 404 on login when using valid credentials.

    TL;DR: The issue is related to a mismatch between the username - an email address, complete with @ - and the user slug, which replaced the @ with a _ for some reason.

    Relevant Versions

    VS Code: 1.38.1
    atlascode plugin: 2.0.0b2
    Bitbucket Server: 6.1.8 (no admin access)

    Details

    The issue had to do with the construction of siteDetailsUrl. The generated URL looked like this:

    https://bitbucket.company.com/rest/api/1.0/users/user@company.com?avatarSize=64

    This returning a 404, which I verified in Postman. While I was poking around with the REST API, I hit the users endpoint and got a list of users. The problem popped up right away.

    {
  "size": 25,
  "limit": 25,
  "isLastPage": false,
  "values": [
    {
      "name": "user1@company.com",
      "emailAddress": "user1@company.com",
      "id": 111,
      "displayName": "User One",
      "active": true,
      "slug": "user1_company.com",
      "type": "NORMAL",
      "links": {
        "self": [
          {
            "href": "https://bitbucket.company.com/users/user1_company.com"
          }
        ]
      }
    },
    {
      "name": "user2@company.com",
      "emailAddress": "user2@company.com",
      "id": 112,
      "displayName": "User Two",
      "active": true,
      "slug": "user2_company.com",
      "type": "NORMAL",
      "links": {
        "self": [
          {
            "href": "https://bitbucket.company.com/users/user2_company.com"
          }
        ]
      }
    },
    {
      "name": "user3@company.com",
      "emailAddress": "user3@company.com",
      "id": 113,
      "displayName": "User Three",
      "active": true,
      "slug": "user3_company.com",
      "type": "NORMAL",
      "links": {
        "self": [
          {
            "href": "https://bitbucket.company.com/users/user3_company.com"
          }
        ]
      }
    }
  ]
}

    Since the API wants the user’s slug instead of their username, the mismatch triggered the 404.

    The outcome of the failure was a bit confusing, since the logger indicated an authentication error.

    [2019-09-30 21:58:50:903] [Atlassian] undefined Error: Authentication error: Error authenticating with Bitbucket: Error: Request failed with status code 401

    I spent awhile chasing my tail trying to make sure the credentials were right and that my account hadn’t been locked out or something. It wasn’t until I cloned the project and ran it in debug that I actually saw the URL it got a 404 on.

    If I had admin rights on the server I probably could’ve pored over the logs to see the 404 and the URL there too. But like many devs using enterprise Bitbucket servers I’m not an admin.

    I hope this helps. For now I’m just using the 2.0.0b2 version with a one-line code change to accommodate my oddity.

    This is the original HTTP REST call from loginManager.ts :

    const res = await transport(siteDetailsUrl, {
    method: "GET",
    headers: {
        "Content-Type": "application/json",
        Authorization: authHeader
    }
});

    And this is the quick hack that got my company’s Bitbucket server working for me:

    const res = await transport(siteDetailsUrl.replace("@", "_"), {
    method: "GET",
    headers: {
        "Content-Type": "application/json",
        Authorization: authHeader
    }
});

    ‌

  100. Jonathan Doklovic Account Deactivated

    @Jesus Martinez Fernandez I think the problem with google login is that Jira doesn’t have a passowrd set for your user in it’s internal database. Could you try logging out of jira, then get to the login screen and use the “Can’t login?” link? This should send you a reset password email for Jira’s internal database (not changing your google password). After you set a password, you should be able to login with the extension using your google account username/email and the password you set in jira.

    Keep in mind this is just a workaround to test. Using an app password like @{557058:a30b5736-f3cf-41d7-aad0-99c9ffac78ce} suggested should work.

  102. Jonathan Doklovic Account Deactivated

    @Jesus Martinez Fernandez Ok, it was just a thought. Unfortunately there are many plugins that provide SAML auth for Jira and there’s no way for our external extension to tap into that flow as far as we know. The best bet is going to go down the app password route. We’ll keep investigating here and see if there’s anything we haven’t tried yet.

  103. Jesus Martinez Fernandez

    Thanks @{557057:3695b794-cde3-43a2-99aa-c0fc6151b754} , I didn’t have the chance to try the plugin yet but it looks really cool, you’re doing a great job guys!

  104. Nick Rundquist

    Version 2.0.0 is now available on the VS Code Marketplace. It will allow you to use the extension with Bitbucket Server and Jira Server along with Bitbucket Cloud and Jira Cloud.

  106. Gabriel Knauth

    Is anyone else having issues authenticating with the server?  I’m simply receiving an Unauthorizedresponse, despite being able to connect prior to the update.

  107. Jonathan Doklovic Account Deactivated

    @Gabriel Knauth Which version previously worked and which version isn’t working? Also, are you trying to auth with Jira or Bitbucket?

  108. Gabriel Knauth

    @Jonathan Doklovic I reinstalled Atlassian for VSCode on Wednesday and it was working on Wednesday and Thursday. 

    Atlassian for VS Code automatically updated this morning to the latest version (with the new Authentication options). 

    I am trying to log into Jira Cloud.  I haven’t tried Bitbucket yet (we have server BitBucket).

  109. Jonathan Doklovic Account Deactivated

    @Gabriel Knauth seems like this may be an issue during the upgrade migration. Can you please log a new issue for this and we will help you debug. The first thing to try is to click the trash icon next to your Jira site in the settings screen and then try to re-authenticate. If that doesn’t work, we can walk you through clearing out the previous data and logging in again.

  110. Gregory Warnes - Huntersville

    Unfortunately, the current version only supports access via https endpoints. Since our locally hosted Bitbucket and Stash servers only support http access, I still can’t use it.

    I created ticket #199 to track this issue.

  111. Ksawery Karwacki

    It works like a charm but unfortunately it is unusable for me due to #80. Also plugin doesn’t load avatars

  113. Austin Eldridge

    @Pramod Busam - I am having the same issue as Fredrik Averpil “Error authenticating with Bitbucket: Error: Request failed with status code 400”. I believe this is a proxy or SSL certificate issue because the curl command with the link you provided works fine. Any advise on how I can debug?

    ‌

  114. Jack Koppa

    Huge, huge thank you to the Atlassian team for tackling this. We’re now using the extension without issue on Bitbucket + JIRA Server, and our team is loving it thus far. Thank you! 🙇‍♂️

  115. Jason Templeman

    I too have the same issue as @Austin Eldridge and @Fredrik Averpil I expect this to be a SSL Cert issue but don’t see any fix/suggestions here. Assuming this is fixed so can someone point me to instructions on how to correct this error?

  116. Jonathan Doklovic Account Deactivated

    @Jason Templeman Usually if there are SSL issues, it’s cause by having a custom, self-signed cert in your chain. If your company uses such a cert, you can add it when you configure the authentication in VSCode. There should be a switch to “Usee Custom SSL Cert” in the settings page.

  117. Jason Templeman

    @{557057:3695b794-cde3-43a2-99aa-c0fc6151b754} Thanks but what goes there? Seems everything I try doesn’t work. Getting failed with status code 400. Is there a way to get debug output? What command is being sent (can I send it thought a console to debug)?

    ‌

  118. Jonathan Doklovic Account Deactivated

    @Jason Templeman Can you please open a separate issue for your auth issue so we can work with your specifics?

    Thanks!

  119. Austin Eldridge

    @Jason Templeman - here are the instructions that were put together after I finally worked through this. I’ve removed some employer specifics to protect the innocent :). Hopefully, you’re biggest opportunity will be getting a hold of the correct certificate with these instructions.

    ‌

    # VSCode and Atlassian Issues/Pull Requests

For any work that needs to be done using COMPANY's on-prem Atlassian stack, these extensions and integrations into VSCode make things significantly smoother.

## Pre-requisites

- [Jira and Bitbucket VSCode Extension](https://marketplace.visualstudio.com/items?itemName=Atlassian.atlascode)

## Set Up Atlassian Account

1. A "Getting Started" window should open for configuring access to Jira/Bitbucket
2. Use the `Add Custom Jira Site` and `Add Custom Bitbucket Site` buttons
3. Set Up Custom Jira Site

    - For the baseurl, put: `https://jira-prod.subdomain.company.com/`
    - Enter your username and password (username will be your E/C number)
    - Check the box for `Use Custom SSL Settings`
    - Select the option for `Use custom CA certificate(s) (e.g. a self-signed cert)`
    - Download the custom cert from [here](http://pki.COMPANY.com/crl/COMPANY%20General%20Purpose%20Issuing%20CA%203.crt). File will immediately download.
    - Enter the absolute path on your local computer to the downloaded cert. For instance, mine was:
        `/Users/xiou/Documents/COMPANY/COMPANY General Purpose Issuing CA 3.crt`

        - Tip: The Extension does **NOT** tolerate properly escaped paths.  For instance, `/Users/USERNAME/.certificates/COMPANY\ General\ Purpose\ Issuing\ CA\ 3.crt` will cause you **Authentication Error** problems.

    - Click Save

4. Set Up Custom Bitbucket Site

    - For the baseurl, put: `https://bitbucket-prod.subdomain.company.com/`
    - Follow the other steps from the Jira configuration

5. Click Done
6. Update the Connectivity Settings on the General tab to the correct endpoints.

   - If this is not done, you may encounter `Looks like you've gone offline` errors even if your connectivity is fine.

   ![Atlassian Connectivity Settings](./images/AtlassianConnectivitySettings.png)

7. Click on the Icon in the Left Hand Bar for Atlassian. Now, you should be able to do pull requests and manage issues from VSCode.

    ![Atlassian Toolbar](./images/AtlassianVSCode.png)

## Debugging Connectivity Issues

Debug logging and curl logging for the extension are very useful for debugging any errors.

Search for `atlascode.outputLevel` and `atlascode.enableCurlLogging` in VS Code's settings to view/update the log level.  You can then select `Atlassian` in the dropdown in VS Code's output panel to see the logs to troubleshoot your issues.

    ‌

  120. Jason Templeman

    @Austin Eldridge Thanks for the great write up. I followed the directions, was able to get our General Purpose Issuing CA 3.crt file but as soon as I click Save it get an Authentication error of “Error authenticating with Jira: Error: Request failed with status code 400” Same when trying Bitbucket.

    FYI I am using Windows 10. I say this because the patch to the cert you showed looks more like a Linux path. I do have a Linux system available and going to try this there to see if I get the same results while waiting for a reply

    ‌

    UPDATE - Getting the same results on me Linux system

    Enabled debug mode and this is the only thing in the logs regarding this.
    [2020-06-25 01:43:37:934]   Error: Error authenticating with Jira: Error: Request failed with status code 400
    [2020-06-25 01:43:37:934]  Error: Authentication error: Error authenticating with Jira: Error: Request failed with status code 400

    ‌

    Enabled curl output and see this in the log
    curl -X GET -H "User-Agent:atlascode/2.x axios/0.19.2" -H "X-Atlassian-Token:no-check" -H "Content-Type:application/json" -H "Authorization:Basic XXXXXXXXXXXXXXXXXXXX" "https://jira-prod.subdomain.company.com/rest/api/2/myself"

    Error: Error authenticating with Jira: Error: write EPROTO 3701383416:error:100000f7:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER:../../third_party/boringssl/src/ssl/tls_record.cc:242:

    Error: Authentication error: Error authenticating with Jira: Error: write EPROTO 3701383416:error:100000f7:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER:../../third_party/boringssl/src/ssl/tls_record.cc:242:

    I’m seeing the cert error in Postman as well. It does work OK when I turn off SSL certificate verification.

    ‌

  121. Austin Eldridge

    Unfortunately, looks like the instructions are good (I’m a macOS user, but our Windows users have used these instructions successfully) and you’ve got some kind of an SSL cert issue. Probably need to followup with your corporate IT / Atlassian directly - I won’t be able to provide any additional guidance.

  123. Log in to comment
Assignee
Type
enhancement
Priority
major
Status
resolved
Component
–
Votes
269
Watchers
197