git-ecosystem / git-ecosystem/git-credential-manager
OAuth not supported in multiple users setup
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9.3k
- Forks
- 2.9k
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 14
Description
Version
2.4.1
Operating system
Windows
OS version or distribution
Windows 10 Pro (x64)
Git hosting provider(s)
GitLab
Other hosting provider
No response
(Azure DevOps only) What format is your remote URL?
None
Can you access the remote repository directly in the browser?
Yes, I can access the repository
Expected behavior
I followed the multiple-users.md to setup different identities and expected GCM to use OAuth-Authtenfication for each similiar identity based on username and host.
Actual behavior
GCM is prompting on each git operation for authentication and is registering as "new" OAuth-application.
OAuth authentication is not supported in a multiple users setup?
As I can see Windows Credential Manager doesn't store any information that could be used by GCM to match stored OAuth-Key with an specific user.
Logs
No response
Contributor guide
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.
Research direction
Start by reading multiple-users.md and reviewing how OAuth credentials are stored and matched through Windows Credential Manager. Confirm the behavior with multiple GitLab identities. Done means each identity can use OAuth without repeated prompts or registration as a new OAuth application.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100