RE: unable to login to svn repo

Thanks Thorsten and Ryan. I have turn on the logging and now on server itself I issue the following command:
 - svn co svn://192.168.4.64/home/RKapur/repo3

I see this in the sever log file:

1190 2012-07-24T14:29:51.004017Z 192.168.4.64 harry home/RKapur/repo3 open 2 cap=(edit-pipeline svndiff1 absent-entries depth mergeinfo log-revprops) / SVN/1.6.11%20(r934486) -
1190 2012-07-24T14:29:54.920106Z 192.168.4.64 harry home/RKapur/repo3 get-latest-rev
1190 2012-07-24T14:29:54.920247Z 192.168.4.64 harry home/RKapur/repo3 reparent /
1190 2012-07-24T14:29:54.920336Z 192.168.4.64 harry home/RKapur/repo3 ERR subversion/svnserve/serve.c 167 170001 Authorization failed

Also when I said the above command - svn client side communications is as follows:

[rkapur_at_nyc-devhieapp01 client]$ svn co svn://192.168.4.64/home/RKapur/repo3
Authentication realm: <svn://192.168.4.64:3690> repo3_realm
Password for 'rkapur':
Authentication realm: <svn://192.168.4.64:3690> repo3_realm
Username: harry
Password for 'harry':

-----------------------------------------------------------------------
ATTENTION! Your password for authentication realm:

   <svn://192.168.4.64:3690> repo3_realm

can only be stored to disk unencrypted! You are advised to configure
your system so that Subversion can store passwords encrypted, if
possible. See the documentation for details.

You can avoid future appearances of this warning by setting the value
of the 'store-plaintext-passwords' option to either 'yes' or 'no' in
'/home/RKapur/.subversion/servers'.
-----------------------------------------------------------------------
Store password unencrypted (yes/no)? yes
svn: Authorization failed
[rkapur_at_nyc-devhieapp01 client]$

Now 1) as you see above it always challenge me for "rkapur" password - I think its because first I login this linux box as "rkapur" and then did "su - some_other_user" - so therefore its always somehow ask me for "rkapur" password. After then it ask me for username for which then I said "harry" and the default password as in the file. I am sure I typed in correct password as in file but still gives this error. Thanks for your help.
-raj.

-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2012c_at_ryandesign.com]
Sent: Tuesday, July 24, 2012 3:57 AM
To: Thorsten Schöning; Kapur, Rajneesh
Cc: users@
Subject: Re: unable to login to svn repo

On Jul 23, 2012, at 16:41, Thorsten Schöning wrote:

> Guten Tag Kapur, Rajneesh, am Montag, 23. Juli 2012 um 22:45 schrieben Sie:
>
>> C:\Program Files\CollabNet\Subversion Server>svn co svn://172.20.212.6/u01/app/repo3
>> Authentication realm: <svn://172.20.212.6:3690> repo3_realm
>> Password for 'rkapur':
> [...]
>> 4) Contents of passwd file are:
>> [users]
>> harry = harryssecret
>> sally = sallyssecret
>
> You can't login with rkapur without providing user credentials for
> this user in passwd.

You snipped the part where he showed that he subsequently logged in as harry, a user who is in the password file:

> On Jul 23, 2012, at 15:45, Kapur, Rajneesh wrote:
>
>> C:\Program Files\CollabNet\Subversion Server>svn co svn://172.20.212.6/u01/app/repo3
>> Authentication realm: <svn://172.20.212.6:3690> repo3_realm
>> Password for 'rkapur':
>> Authentication realm: <svn://172.20.212.6:3690> repo3_realm
>> Username: harry
>> Password for 'harry': ************
>> svn: E170001: Authorization failed

Check the server log file to see why authorization failed. You may first have to turn on logging on the server and then repeat the checkout attempt.

IMPORTANT WARNING: Information contained in this email is intended for the use of the individual to whom it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is STRICTLY FORBIDDEN. If you have received this communication in error, please notify us immediately by return email and delete this document. Thank you.
Received on 2012-07-24 17:11:18 CEST