git-ecosystem / git-ecosystem/git-credential-manager

Git Credential Manager is flushed out if user tries to access unauthorized repo

Open
#2,095 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

auth-issue host:github platform:linux
Dominant language
C#
Stars
9.3k
Forks
2.9k
Avg merge
7d 1h
Merged PRs (30d)
14

Description

Version

2.6.1+786ab03440ddc82e807a97c0e540f5247e44cec6

Operating system

Linux

OS version or distribution

RHEL 8

Git hosting provider(s)

GitHub

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 am able to access the Github repos and clone them when I set the GCM with plaintext. But by mistake if I try to access a repo for which I don't have access, then I get multple popups for giving the credentials, whereas I had already set and saved it in plaintext. When I check the details after that I see that the credentials are already deleted from the saved space. If I try to access an unauthorized repo, then it should only show that you are not authorized and it should not flush out the details stored.

Please help here

Actual behavior

I am able to access the Github repos and clone them when I set the GCM with plaintext. But by mistake if I try to access a repo for which I don't have access, then I get multple popups for giving the credentials, whereas I had already set and saved it in plaintext. When I check the details after that I see that the credentials are already deleted from the saved space. If I try to access an unauthorized repo, then it should only show that you are not authorized and it should not flush out the details stored.

Logs

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue on Linux/RHEL 8 with Git Credential Manager 2.6.1, GitHub, and plaintext credential storage, using an unauthorized repository. Trace the authentication failure and credential-removal path; done means an unauthorized access attempt reports the failure without deleting valid stored credentials, while existing repository access continues to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, git, github
Domain
authentication, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.