git-ecosystem / git-ecosystem/git-credential-manager
Intermittent authentication failures
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.6.0
Operating system
Linux
OS version or distribution
NixOS 24.11
Git hosting provider(s)
Other - please describe below
Other hosting provider
gitea via oidc
(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
GCM should execute my git command without failing
e.g. git push -> exit code 0
Actual behavior
My git command fails and only succeeds when I retry it.
This issue is intermittent, i.e. it probably is related to OIDC token refresh or libsecret.
❯ git push
remote: Verify
fatal: Authentication failed for 'https://XXXXXXX'
❯ git push
Enumerating objects: 11, done.
Counting objects: 100% (11/11), done.
Delta compression using up to 12 threads
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 628 bytes | 628.00 KiB/s, done.
Total 6 (delta 3), reused 0 (delta 0), pack-reused 0 (from 0)
remote: . Processing 1 references
remote: Processed 1 references in total
To XXXXXX
8c477eb..55b2799 main -> main
Logs
I will attach some logs as soon as I run into the error again
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
No source file or test is named. Reproduce the first-attempt failure on NixOS 24.11 with Gitea via OIDC, then capture the promised logs and investigate the suspected OIDC token refresh or libsecret path; done means git push succeeds without a retry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git, linux
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100