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

account filtering filters out my account, requiring re-authentication for every action

Open
#1,639 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Version

2.5.0.0

Operating system

Windows

OS version or distribution

Windows 11 Pro (x64)

Git hosting provider(s)

Other - please describe below

Other hosting provider

GitHub Enterprise Cloud

(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

After executing git fetch in the command line, I expect git fetch to work normally.

Actual behavior

After executing git fetch in the command line, the authentication dialog box shows up every time. If I authenticate using "browser", git fetch succeeds, and then the next time I git fetch, the dialog box pops up again. The credential is visible through Windows Credential Manager, and I can confirm that the successful authentication causes it to be added. This only happened on upgrade to git for windows 2.45.2, from 2.41.0.

After executing git config --global credential.githubAccountFiltering false in the command line, git fetch works as expected.

After executing git config --global credential.githubAccountFiltering true in the command line, the authentication dialog plague returns.

Just to confirm, the remote is on GitHub Enterprise Cloud.

Logs

failure with logging.txt
filtering-disabled.txt

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 git fetch on Windows 11 with Git for Windows 2.45.2 and credential.githubAccountFiltering enabled, then compare the attached failure with logging.txt and filtering-disabled.txt logs. Done means a successful browser authentication is reused on the next fetch against GitHub Enterprise Cloud without another authentication dialog.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.