Visual Studio Code doesn't prompt for password correctly

[madisonjsmith]

Issue Type: Bug

Visual Studio Code doesn't prompt for password correctly when using the new Git credential manager core (credential.helper=manager-core)

Environment setup: Connecting to on prem bitbucket server using Active Directory credentials Connect successfully for the first time using a test AD account then change the password on the test account. Try to do a new push via the Source Control GUI menu "push" option:

The push will fail due to invalid credentials. No dialog window is displayed to enter in the new password.

Work around: at the terminal/command line, a manual "git push" command will display a windows dialog asking for the credentials.

VS Code version: Code 1.54.3 (2b9aebd5354a3629c3aba0a5f5df49f43d6689f8, 2021-03-15T10:55:45.459Z) OS version: Windows_NT x64 10.0.19042

System Info

|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz (4 x 2295)| |GPU Status|2d_canvas: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled| |Load (avg)|undefined| |Memory (System)|7.88GB (1.79GB free)| |Process Argv|--crash-reporter-id 7b902153-8377-4521-94bb-2451e95bbd21| |Screen Reader|no| |VM|40%|

Extensions (6)

Extension|Author (truncated)|Version ---|---|--- jenkinsfile-support|ivo|1.1.0 jenkins-pipeline-linter-connector|jan|1.2.0 csharp|ms-|1.23.9 remote-wsl|ms-|0.54.6 powershell|ms-|2021.2.2 json|Zai|2.0.2

A/B Experiments

``` vsliv368:30146709 vsreu685:30147344 python383cf:30185419 pythonvspyt700cf:30270857 vspor879:30202332 vspor708:30202333 vspor363:30204092 vstry244:30276681 pythonvsdeb440:30248342 pythonvsded773:30248341 pythonvspyt875:30259475 pythonvsnew554cf:30277039 pythontbcf:30265426 vscoresta800cf:30276762 vspre833cf:30267465 vsdfh931:30275552 vshan820:30276952 ```

[fmarslan]

I have same problem on the linux OS and I tried somethings. if I add credential for global config like following sample and store my credential information, it's work. The solution can use temporary.

.gitconfig

[credential]
    helper = store --file ~/.git-credentials
    helper = cache --timeout 30000

.git-credentials

https://username:password@yourgitserver

note: if you delete your credential from .git-credentials, will be added again by vscode when it's run. actually this is bug too :)

[Rollbacke]

Same problem here (Debian 11). It's very annoying. I don't know since which version the problem appeared.

[Aaqib925]

Yes, this issue is very annoying on Linux OS, from the last version updates I am facing this bug. Also I have tried every other stackoverflow solution, but it doesn't work at all :(.

[Seairth]

@fmarslan @Rollbacke @Aaqib925 See issue #137063.

[fmarslan]

Latest release fixed the bug for me

Version: 1.62.3 Commit: ccbaa2d27e38e5afa3e5c21c1c7bef4657064247 Date: 2021-11-17T08:00:36.721Z Electron: 13.5.2 Chrome: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Linux x64 5.11.0-41-generic

[jadelynnmasker]

problem still exists with version 1.63.2 on windows

[jadelynnmasker]

also has same problem with gpg signatures

[aedjoel]

Same issue here

[russmenum]

Did we ever get a fix for this? I was using Atom, but the MS GitHub overlords decided we must all now use VSCode.

In my case, it is a self-hosted repo on our own servers, password not to be stored and manually entered each request: fetch, pull, push...

On Atom I got a prompt for the pass every time to enter, on VSCode all interactions with the repo FAILS because it never asks for the pass it needs to authenticate.

[lszomoru]

Is anyone is still able to reproduce this issue given that there were improvements done in this area? Thanks!

[russmenum]

Is anyone is still able to reproduce this issue given that there were improvements done in this area? Thanks!

I am still having it here, but on an older Mac that I cannot/should not update... I will be testing a new system in the next month or so with the current VS Code since Atom was terminated...

[vscodenpa]

Hey @lszomoru, this issue might need further attention.

@madisonjsmith, you can help us out by closing this issue if the problem no longer exists, or adding more information.

[vscodenpa]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!