Restart of VSCode requires new login of Atlassian Extension

[Benjamin Heinke]

I’m using VSCode and Kubuntu and the official Atlassian Extension. But whenever I restart VSCode or simply open a new folder it logs me somehow out of the extension. In the bottom bar I see again:”Sign in to Jira” and “Sign in to Bitbucket”. But going to the authorization section of the extension settings shows my repository but I am not logged in.

[Nick Rundquist]

It sounds like your credential information isn’t getting saved. We use the keytar library to save this information in the password service supplied by the OS. In the case of Linux libsecret is always the method I’ve seen used. Seeing as that's a Gnome library it's possible that it wouldn't be installed on Kubuntu.

There might be more information about what’s going wrong on the terminal. You can enable logging with the following steps

• Open the settings for VS Code and search “output level”, there will probably be a few results, one of them should be “Atlassian” in the “Extensions” section.
• Set the output level to “debug”.
• If you don’t already have a terminal open in VS Code, select New Terminal from the Terminal menu.
• Select the “Output” tab in the terminal”.

‌

[Benjamin Heinke]

@Nick Rundquist Thanks for the response. This might be the issue but I’m not sure how to solve it. I set the output level of Atlascode (Atlassian) to debug. I restarted VSCode and logged in again, but didn’t have any message in the output tab of the terminal in VSCode. I only get the error from Jira and from bitbucket: cannot get client from Jira.

[Nick Rundquist]

Looks like it should work if you install gnone-keyring. Try running sudo apt install gnome-keyring and then going through the process of adding the sites again. When you’re directed back to the application after the OAuth prompt you might also get a dialog asking you to create a password for the keychain. This prompt is from the keyring service so whatever password you enter can be unrelated to your Atlassian password.

‌

[Benjamin Heinke]

@Nick Rundquist Thanks a lot, that fixed the issue! Great!

[Benjamin Heinke]

Issue fixed