TortoiseSVN Authorization failed on commit, but only from my machine

1,175 views
Skip to first unread message

mar coulrob

unread,
Mar 10, 2021, 11:23:06 AM3/10/21
to TortoiseSVN

I try to use TortoiseSVN on Windows 10. When I try to commit I get an "Authorization failed" error.

I use the followinf SSH client: C:\Program Files\TortoiseSVN\bin\TortoisePlink.exe -a -P 9222 -l <my id> -pw <my password>. And I get the same error when I retry as different user and input my credentials in the dialog box.

And the problem mustn't lie in the repository: a colleague who uses my credentials manages to commit on his machine.

Stefan

unread,
Mar 10, 2021, 11:48:56 AM3/10/21
to TortoiseSVN
if the authorization failed, that means the authentication was successful (i.e, your username/password is ok), but the user does not have the rights to do what you want to do.
That's definitely on the server side - maybe you want to commit something where you don't have write access to?

mar coulrob

unread,
Mar 10, 2021, 12:09:08 PM3/10/21
to TortoiseSVN
Server side? But my colleague manages to commit with my credentials. I've tried to modify (and commit) the same file than him.

mar coulrob

unread,
Mar 11, 2021, 12:49:33 PM3/11/21
to TortoiseSVN


If it can help, all my repertories in C:\Users\<myUsername>\AppData\Roaming\Subversion\auth (which are svn.simple, svn.ssl.client-passphrase, svn.ssl.server and svn.username) are empty.

Stefan

unread,
Mar 11, 2021, 3:39:35 PM3/11/21
to TortoiseSVN
On Thursday, March 11, 2021 at 6:49:33 PM UTC+1 marco...@gmail.com wrote:
If it can help, all my repertories in C:\Users\<myUsername>\AppData\Roaming\Subversion\auth (which are svn.simple, svn.ssl.client-passphrase, svn.ssl.server and svn.username) are empty.

 those files are only used for http/https connections.
svn+ssh connections can't store any auth data because that's handled exclusively by ssh and your ssh tool.

But as I explained: authorization failed means you don't have the priviledges to do what you want. It's not a problem of authentication (note the difference: authorization vs. authentication).
And such an error is only returned by the server - it has nothing to do with the client.
If you have access to the log files on the server, you should check those - maybe you find something in there that might help.

mar coulrob

unread,
Mar 11, 2021, 3:52:47 PM3/11/21
to TortoiseSVN
I see the difference between authorization and authentication but I get the same error when I enter random credentials.

If it's a server error, how do you explain that my colleague managed to commit with my credentials with his machine?

I already asked for access to the log files on the server, but there was reluctance.

Stefan

unread,
Mar 11, 2021, 4:11:29 PM3/11/21
to TortoiseSVN
On Thursday, March 11, 2021 at 9:52:47 PM UTC+1 marco...@gmail.com wrote:
I see the difference between authorization and authentication but I get the same error when I enter random credentials.

Then that's definitely a server problem. Seems the server accepts any user, but then rejects access to unknown users.
 

If it's a server error, how do you explain that my colleague managed to commit with my credentials with his machine?

different IP adresses?
 

I already asked for access to the log files on the server, but there was reluctance.

I know the feeling... IT departments are in my experience usually very hard to deal with...

But in this case: explain your problem to them and tell them that you need this to work for you to get your work done. Then they have to do something about this.
If that doesn't work, tell your superior about your problem, and I guess that will make the IT guys to actually look into the problem.
At least that's how I usually get similar problems solved...


mar coulrob

unread,
Mar 15, 2021, 4:27:23 PM3/15/21
to TortoiseSVN
The problem is solved. In fact, I was given an erroneous link to checkout.

Thanks for your help

Reply all
Reply to author
Forward
0 new messages