All connection passwords erased if view settings json users

[kurtdl23]

Describe the bug

If you have several connections setup where you check the save passwords, if you go in and modifiy the user settings json for another setting, and save, the passwords are gone in the saved connections

To Reproduce

Steps to reproduce the behavior:

1. Create several connections with SAVED passwords
2. go to command palette and open user settings JSON
3. add a setting unrelated to pgsql
4. Save
5. Try to open previously saved connections, they will fail

Expected behavior

Should have behaved the same way for when I created the connection.

Screenshots

If applicable, add screenshots to help explain your problem.

VS Code version

Version: 1.109.1 (user setup)
Commit: 6534f6ba7604bf324f94cc9a590727f39a4af040
Date: 2026-02-09T20:18:48.496Z
Electron: 39.3.0
ElectronBuildId: 13168319
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Extension Logs

didn't want to share for security reasons ,will pull information if needed.

[mmcfarland]

Hi @kurtdl23 -- thanks for reporting this issue. I'm having trouble reproducing the issue, though. Here's what I've tried, can you spot any difference in repro steps?

1. Windows 11 / extension version 1.16.0
2. Add local docker PG instance with password, ensure "save password" is selected
3. Connect / reconnet -- doesn't prompt for password. Password still visible in connection editor dialog
4. Add an arbitrary setting in user settings (I'm using "workbench.activityBar.location": "bottom"), save.
5. Try reconnecting to the server from 2. I still get a connection without password prompt
6. Restart vscode, I still have the password saved

Any other insights would be really helpful. Do you have any errors in our Output pane for the "PostgreSQL (Microsoft)" extension?

I will note that the key used to look up a saved password from VS Code's SecretStorage API is a concatonation of server properties (host, port, user, etc) so if those values change, it may require re-entering the password. But it doesn't sound like you're editing the profiles of the connections that are affected.