Unable to change authentication credentials in VSCode extension.

[Ian Wilkinson]

We are using Jira server with AD accounts, but this issue is not limited to AD accounts, just worse as the delay from updating password to Jira seeing the new password is unknown.

For the avoidance of doubt, when I say “Change password” I mean that the user has actually changed their password in Jira/AD

when I say “Update password” I mean the act of putting the new password into the extension.

‌

When the password for the user is changed, the extension seems to get stuck in a loop and repeatedly tries to authenticate without realising that there’s an issue.

This causes the Jira server to request a CAPTCHA.

At this point it is almost impossible for the user to be able to change their password in the plugin:

1. The plugin will not save a new password unless the authentication was successful.
2. Due to this, the user cannot update the password in the plugin before changing their password.
3. User changes password,
4. Plugin tries to use old password (seemingly as soon as it has focus) causing a failed login attempt.
5. Plugin seems to keep trying to use bad password.
6. Server now requires CAPTCHA
7. User tries to update password in extension, but it won’t save as the server requires CAPTCHA causing authentication failure.

‌

Suggested solution:

As soon as any call has an authentication issue block all future calls.

Popup a Toast informing the user, and allowing the user to retry or go to the settings screen to update their credentials.

If authentication fails after entering new details, send user to Jira website to pass CAPTCHA, then allow them to retry the updated credentials.

‌

Current work-around:

Open authentication edit screen, update password, but do not hit save.

In Jira website, logout, login (answer CAPTCHA), and as soon as you are in, hit save in extension.

The order of events is critical, and must be done quickly before the extension locks the account again.

[Josue Sanchez Vazquez]

Thanks for the workaround @Ian Wilkinson . We hope it will be fixed asap!

[RICHARD CROSS]

Having the same problem every time I relaunch Visual Studio Code on Windows; the Atlassian extension seems stuck on an old password, so I have to go through that workaround every day.