scalar: Scalar clone fails with "http 401: Not authorized: from POST) from Azure Devops Server 2019
Running Azure DevOps Server Version Dev17.M153.5.
I have a 4.5 GB git repo that I uploaded to our on prem azure devops server via normal git push. I then tried to use `scalar clone https://ourserver.domain.name/OurCollection/OurProj/_git/reponame.git. A popup window asked me for my creditials, which I provided, and then I got this message:
Attached here is the log from .git/logs/scalar_clone_*.log.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 1
- Comments: 28 (12 by maintainers)
Problem was my bad. I had a typeo in the hostname. This is legit fixed.
@derrickstolee It works! Thank you!
Thanks for the confirmation.
Thanks for the logs. I’m going to dig into this and try to repro it.
@derrickstolee I have dumped a traffic of scalar clone scenario (by MITM SSL proxy):
As we can see /gvfs/objects request doesn’t try to use NTLM. It asks password and uses plain text authentication. (Not sure if it is allowed in Azure DevOps) It is a reason of the bug probably.
Thanks for the clarification. We’ll continue to dig in.
Thanks! The strange thing is that you are getting a 200 response from the
gvfs/configrequest, but somehow not from thegvfs/prefetchrequest. It may be a difference between the C# layer making a request and getting good authentication versus the Git client using thegit-gvfs-helpernot getting the same auth mechanism.@jeffhostetler: have you seen this sort of issue?
@jrbriggs: Do you know if there is a reason we would purposely send a 401 in Azure Repos based on a config setting or something?