Password in Windows credentials is not updated on next `set_password` call
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- authentication
Research direction
Start with the Windows.WinVaultKeyring backend listed by keyring --list-backends, then reproduce the two keyring set_password calls on Windows and inspect the resulting Credential Manager entries. Compare the CLI path with the direct Python keyring.set_password path; done means the second call updates the existing credential rather than creating a second entry.
Written by the indexing model from the issue text.
Description
Describe the bug
New entry is created instead of updating existing password.
To Reproduce
-
Open cmd.exe and set password with CLI utility
C:\>keyring set service username Password for 'username' in 'service': <enter the password> -
Open Credential manager and observe a new entry:

-
Update password. Open cmd.exe again and set new password with CLI utility for the same service and user name
C:\>keyring set service username Password for 'username' in 'service': <enter another password> -
Refresh Credential manager's window and see two entries:
serviceandusername@service
Expected behavior
Second call for keyring set service username should modify existing entry instead of creating new one.
Environment
- OS: Windows 10 Pro with all recent updates.
C:\> pip list | grep keyring
keyring 23.2.1
C:\> keyring --list-backends
keyring.backends.Windows.WinVaultKeyring (priority: 5)
keyring.backends.chainer.ChainerBackend (priority: -1)
keyring.backends.fail.Keyring (priority: 0)
Additional context
The same behavior is observed in call to keyring.set_password in python scripts.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 208
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jaraco/keyring
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
macOS: denied keychain prompt on delete raises PasswordDeleteError instead of KeyringLockedPossibly taken @r3wretrhy claimed this 46 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Remove B018 suppressions after adopting skeleton's B018 ignorePossibly taken @Madin-H23 claimed this 26 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 78/100
Similar issues
-
cognition facet:consolidation memory ready size:S
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
proposal
Difficulty 1/5 Under an hour Newbie friendliness 68/100
j3ko/agent-plugins#29 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
-
area:cli area:security bug priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Gathin23/cleanyourtv#4026 ·
Maintainers usually reply within 1 day