Bug: authentication with Jira & Bitbucket is lost after vscode is closed

[Former user]

Hello,

I’ve just installed the extension for vscode.

I've clicked configure Atlassian settings > Authentication > Authenticate with Jira; Authenticate with Bitbucket;

Both times I’ve successfully authenticated through the browser window and everything seems to work fine.

But when I close vscode, the authentication state seems to be lost, because when I launch vscode again, the authentication state is lost - I cannot view my issues / open issues - it requires me to authenticate again. The authentication page also shows that I’m not authenticated neither with Jira nor Bitbucket and asks to authenticate.

---

I’ve done this like 4 times now, and everything’s still the same. I hope that this is not intended.

---

Inside the https://id.atlassian.com/manage-profile/apps , the Atlascode Integration is present,

which might mean that there’re problems with saving the auth tokens for vscode.

‌

---

‌

$ code -v
1.35.0
553cfb2c2205db5f15f3ee8395bbd5cf066d357d
x64

$ uname -a
Linux arch-usb 5.1.9-arch1-1-ARCH #1 SMP PREEMPT Tue Jun 11 16:18:09 UTC 2019 x86_64 GNU/Linux

‌

Extension’s version: 1.4.2

---

Might be related: #7

[brad clements]

I am having a similar problem. Today I am unable to use the vscode plugin, I get “Authentication for jiracloud has been cancelled”

I installed the plugin last friday. I use vscode via ssh, so

‌

1. ssh to laptop and start code-insiders
2. ssh to laptop and start google-chrome-beta
3. in vscode, click ‘sign in to jira’
4. a sign-in window appears in google chrome, I can sign in

Over the weekend I exit vscode and google chrome, suspend the laptop

today I followed the same steps, except no sign-in window appears in chrome.

1. click “sign in to jira” - I wait 10 seconds, nothing appears to happen
2. click “sign in to jira” again, the plugin immediately displays “Authentication for jiracloud has been cancelled”
3. and click “sign in to jira” again, the plugin immediately displays “Authentication for jiracloud has been cancelled”

I also tried signing into Jira cloud in the chrome instance first, before starting vs code. That didn’t make a difference

[Jonathan Doklovic]

The “Authentication for jiracloud has been cancelled” is just an informational message that happens when there’s an auth in-flight and you try to auth again. Since we have no way to determine what’s going on in the OAuth flow, we need to cancel the first request if you start a new auth request.

As for the auth being lost, we currently store the authentication credentials (e.g. your OAuth access and refresh tokens) in you local machine’s keychain.

Sounds like it may be failing to store in the key chain and then gets lost on the next reboot of vscode? We’ll need a little more time to investigate further.

If you could look in your key chain and see if there’s an entry for the extension, that might be useful.

[brad clements]

by keychain, presuming you mean gnome key-ring. I used seahorse on both the laptop (to which I ssh) and the client from which I’m ssh’ing to see if there were any keys mentioning ‘jira’ There weren’t any.

I don’t recall being prompted to unlock my keychain at any point when I first ran the extension last week. Perhaps running vscode over ssh is contributing to the issue.

[Former user]

Same here as Brad:

I'm using gnome key-ring w/ seahorse - haven't found any keys containing jira.

I also wasn’t prompted to unlock my keychain when I ran the extension.

I was running on a local machine, not a remote one.

[Jonathan Doklovic]

I also use gnome key-ring with seahorse and depending on how it’s configured it doesn’t necessarily ask you for the keychain password. (I think by default a daemon is running that bypasses this for you if you’re logged in to a gnome session).

At any rate, the keys are prefixed with “atlascode-authinfo/”
If you don’t see anything like that, then I bet it’s some issue with saving to the keyring when using vscode over ssh.

We’ll be looking into running our extension remotely and fixing any related issues in the near future.

[Former user]

Update:

I haven't installed the gnome key-ring previously and after installing it, also installing secretlib and configuring the keyring with the PAM method and then rebooting - everything works fine as expected - there's a key atlascode-authinfo/jiracloud in seahorse!

---

So that’s it for me, but I’ll leave this issue open because of the remote issues. Feel free to close it if the remote issues are resolved.

‌

Also, you might want to consider checking if the user has a key-ring to save passwords into, because well, I had not:D A helpful error message would save a lot of time, if that’s possible.

‌

Thank you Brad & Jonathan:)