git-ecosystem / git-ecosystem/git-credential-manager
Gitea Oauth not working on Linux
Open
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.4.1
Operating system
Linux
OS version or distribution
Ubuntu 22.04 fresh install
Git hosting provider(s)
Other - please describe below
Other hosting provider
Gitea
(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
Prompt for loging
Actual behavior
Enter basic credentials for 'https://....'
Logs
03:35:08.053205 git.c:455 trace: built-in: git credential-cache get
03:35:08.055785 .../HostProvider.cs:131 trace: [GetCredentialAsync] No existing credentials found.
03:35:08.055797 .../HostProvider.cs:134 trace: [GetCredentialAsync] Creating new credential...
03:35:08.057616 ...ricOAuthConfig.cs:38 trace: [TryGet] Invalid OAuth configuration - missing/invalid authorize endpoint:
03:35:08.057831 ...cHostProvider.cs:104 trace: [GenerateCredentialAsync] Skipping check for Windows Integrated Authentication on Linux.
03:35:08.057842 ...cHostProvider.cs:113 trace: [GenerateCredentialAsync] Prompting for basic credentials...
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
Reproduce the OAuth failure with Gitea on Ubuntu 22.04 and review the credential flow in HostProvider.cs and the OAuthConfig.cs path shown in the logs. Trace why the OAuth configuration is rejected, then verify that the flow prompts for OAuth login rather than basic credentials.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git, linux
- Domain
- authentication, devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100