Unable to add Custom Site

[Arden Hawley]

I am unable to click the “add custom Jira site” button (get a little crossed out circle upon hover). For the record, the ‘login to Jira Cloud’ is also not selectable. Environment details:

• VS Code v1.41.1
• Atlassian plugin v2.3.1
• Will be connecting to a Jira DC instance over https
• Windows 10 and WSL (tried in both environments but no dice)

‌

[Jonathan Doklovic]

@Arden Hawley Currently we don’t support logging in directly from a remote container. This is due to the way we need to receive the auth callback. Fortunately, you can complete the auth locally (not in a remote container) as a one-time process, and then you should be able to use that auth in the remote container.

Let me know how it goes.

[Arden Hawley]

Okay, I’ve retried in my local environment and now get this:

‌

[Jonathan Doklovic]

@Arden Hawley Sounds like your company uses a self-signed cert for your Jira instance. In the login options, you should see an option to use a custom server certificate and you can add the absolute path to the cert when that option is checked.

[Arden Hawley]

It’s checking for the server cert served by my Jira instance, is that correct? I downloaded it to my local machine and now get this when providing its location in the setup. The URL that we access internally is indeed an https URL.

‌

‌

[Jonathan Doklovic]

@Arden Hawley I know this is a silly question, but have you double checked that the url you have in the authentication form starts with https ?

Also, do you know if you’re using a proxy server?

[Arden Hawley]

Not silly haha! I did check and it is https. We do use a corporate proxy and I have VSCode set up for it.

[Jonathan Doklovic]

Ok, in that case, you should see a checkbox on the settings screen that says “Enable https tunneling for proxies”. You should try checking that box. It basically handles cases where there’s a proxy server that accepts http calls to make https calls.

If that doesn’t work, we’ll need to go through some debugging to figure out where it’s failing.

[Arden Hawley]

Yep I have had that checked. Let me know what steps you’d like to take, and I’ll see if I can inspect the traffic.

[Jonathan Doklovic]

OK, let’s start simply.

in VS Code:

1. use the command palette to open “Preferences: Open Settings (UI)”
2. in the search box at the top type: curl
3. find the checkbox for Atlascode: Enable Curl Logging and check it
4. search again for: Output Level
5. find Atlascode:Output Level and make sure it’s set to debug
6. open the bottom pane in VS Code and click on the OUTPUT tab
7. in the dropdown on the right, select Atlassian

With all of that in place, try to auth again with your server.

in the output pane, you’ll see a bunch of curl logging. look for the statement that ends with /rest/api/2/myself

the entire line will look something like:

curl -X GET -H "X-Atlassian-Token:no-check" -H "x-atlassian-force-account-id:true" -H "Content-Type:application/json" -H "Authorization:Basic <removed>" "https://<your domain>/rest/api/2/myself"

copy that entire line and run it in a terminal (making sure the same proxy env vars are active) and see if you get any errors.