Tortoise SVN v1.66 - authorization failed: Could not authenticate to server: could not parse
So a co-worker is having an issue with connecting to a SVN repo over HTTPS. Here are the details:
OS: Windows 7 Enterprise x64
SVN Client: Tortoise SVN 1.6.6 x64
So, whenever he connects (via a fresh checkout (i.e. a clean svn checkout) or update of existing files (i.e. existing working copy)) to the SVN repo in question, he gets the following error:
Error: Unable to connect to a repository at URL
Error: '
Error: OPTIONS of
Error: '
Error: authorization failed: Could not authenticate to server: could not parse
Error: challenge () I had my co-worker try the following things in TortoiseSVN to resolve the issue:
Reset the Authentication Data in Tortoise SVN | Settings | Saved Data for the Authentication Data and URL History,
Checked Proxy Settings in Tortoise SVN | Settings to make sure my co-worker has the same settings that I have on my laptop.
He had the same proxy settings (no settings configured) in TortoiseSVN. Clearing the Authentication Data did not seem to resolve the issue.
I asked my co-worker to log into a spare desktop that is joined to our Active Directory domain with his login credentials and try to checkout a working copy. He was able to check out files, update files, commit files to SVN from the spare desktop. Obviously this issue is not due to my co-worker not having permissions to access the SVN repo since he can communicate with the server from another machine.
So - what / why / where do I have to look on his laptop to resolve this issue? Based on the info contained in the error message, it sounds like something in his SSL certificate on his laptop is screwed up.
I should mention that the SVN server is VisualSVN Server and it is using Integrated Windows Authentication.
Let me know if you need any further info.
Thanks
Richard
2 Answers
Sounds like it this support article could be relevent:
It seems to match all of the conditions that you described. Their fix says:
Since you run VisualSVN Server service under a dedicated user account,
you have to add SPN manually to Active Directory:
1.Logon to a Domain Controller as a domain administrator or as a user
with specific delegated permissions required to modify SPNs.
For additional information on permissions required to modify SPNs
please read the "Delegating Authority to Modify SPNs" Microsoft TechNet article.
2.Start elevated command prompt and enter the following command:
setspn -a http/hostname.contoso.com CONTOSO\username As far as I understand both of the machines are located in the same Active Directory domain. The first steps you should perform to troubleshoot the issue:
- Check the VisualSVN Server log. Do you have any errors there? What are the errors?
- Check the Windows Security log. What events are logged there when authentication fails?
- Can he authenticate with a web browser? E.g. with IE and with FF.
- Do you have the same version of TortoiseSVN on your (or the spare one you've mentioned) and your co-worker's machine?
- What version of VisualSVN Server do you have installed?
Knowing these details you can troubleshoot the authentication issue much faster.
The affected user may need to upgrade to the latest TortoiseSVN 1.6 version in order to solve the issue. I.e. Nevertheless TortoiseSVN 1.6.6 is too outdated and I don't see any reasons to use it now. Consider upgrading at least to TortoiseSVN 1.6.16,
The article "Single Sign-On fails when you run VisualSVN Server under a dedicated user account" does applies only to the case when VisualSVN Server service account works under a dedicated user account since the user account must have SPN assigned in order to authenticate over Kerberos.
Network Serviceaccount has the SPN configured by-default. BTW if you don't see the errorSSPI Challenge failed: The token supplied to the function is invalidon VisualSVN Server log -- SPN is not the root cause.
