You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have Gitea installed on a RHEL8 server [gitea-test.example.org] that is joined to AD. An appropriate HTTP SPN is set up, and Apache is installed there as a reverse proxy to do SSL termination and Kerberos (password-less) authentication. I am able to access this Gitea install using Firefox or MS Edge on my windows workstation. I have also tested using git on a Debian workstation and it authenticates successfully (after obtaining a TGT and setting git config --global http.emptyAuth true).
However, when I try to run git for windows in a standard Command Prompt (cmd.exe) on my windows workstation, I get an authentication failure:
From this line we can see that there is some problem with your local config of the OAuth endpoints. Please can you share your Git config by running the following command?
git config --list --show-scope
Aside:
From the logs I can see that GCM attempts to look for GSSAPI/SPNEGO after failing to use the generic OAuth implementation.
I have also tested using git on a Debian workstation and it authenticates successfully (after obtaining a TGT and setting git config --global http.emptyAuth true).
You mention that you managed to get Kerberos/GSSAPI/SPNEGO working on your Debian machine without GCM. We can also see from the trace logs that we are detecting that this auth mechanism is available.
09:03:06.964487 ...Authentication.cs:44 trace: [GetIsSupportedAsync] Found WWW-Authenticate header for Negotiate
GCM is sending back an empty credential to trigger Git/libcurl's built-in support for Negotiate.. perhaps there is also an issue here with your Git setup on Windows?
Version
2.0.935+8b4735fc7b
Operating system
Windows
OS version or distribution
Microsoft Windows [Version 10.0.19044.2604]
Git hosting provider(s)
Other - please describe below
Other hosting provider
Internal installation of 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
Able to clone/push to Gitea with Kerberos SSO authentication
Actual behavior
fatal: Authentication failed for 'https://gitea-test.example.org/UserName/CodeRepo.git/'
Logs
I have Gitea installed on a RHEL8 server [gitea-test.example.org] that is joined to AD. An appropriate HTTP SPN is set up, and Apache is installed there as a reverse proxy to do SSL termination and Kerberos (password-less) authentication. I am able to access this Gitea install using Firefox or MS Edge on my windows workstation. I have also tested using
git
on a Debian workstation and it authenticates successfully (after obtaining a TGT and settinggit config --global http.emptyAuth true
).However, when I try to run git for windows in a standard Command Prompt (
cmd.exe
) on my windows workstation, I get an authentication failure:Here's the (redacted) trace file contents:
Is there something I'm missing in order to make this work seamlessly?
The text was updated successfully, but these errors were encountered: