RE: unable to login to svn repo

Thanks for pointing it out. I cleaned everything and started fresh with new repo named repo4:

1) svnserve.conf file

[general]
anon-access = none
auth-access = write
password-db = passwd
authz-db = authz
realm = repo4
[sasl]

2) authz file
[aliases]
[groups]
harry_and_sally = harry,sally
[repository:/home/RKapur/repo4]
@harry_and_sally = rw

3) passwd file
[users]
harry = harryssecret
sally = sallyssecret

4) Server log file:

11090 2012-07-24T18:13:22.963843Z 192.168.4.64 harry home/RKapur/repo4 open 2 cap=(edit-pipeline svndiff1 absent-entries depth mergeinfo log-revprops) / SVN/1.6.11%20(r934486) -
11090 2012-07-24T18:13:26.820916Z 192.168.4.64 harry home/RKapur/repo4 get-latest-rev
11090 2012-07-24T18:13:26.821060Z 192.168.4.64 harry home/RKapur/repo4 reparent /
11090 2012-07-24T18:13:26.821156Z 192.168.4.64 harry home/RKapur/repo4 ERR subversion/svnserve/serve.c 167 170001 Authorization failed

5) conversation on client side - I executed the following command on server machine:

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

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

   <svn://192.168.4.64:3690> repo4

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

as it appears that "rkapur" is the user that I am logged in to this linux machine so somehow svn client asks me for that user's password. When I give it - it ignores and ask for username and password - which I gave as "harry" but I still get Authorization failed ? do you think it has to do with some permission because its not authentication error its authorization error. Any where I should look at or how to increase more logging on server side?

Thanks for your time and effort:
-raj.

-----Original Message-----
From: Thorsten Schöning [mailto:tschoening_at_am-soft.de]
Sent: Tuesday, July 24, 2012 1:13 PM
To: Kapur, Rajneesh
Cc: Ryan Schmidt
Subject: Re: unable to login to svn repo

Guten Tag Kapur, Rajneesh,
am Dienstag, 24. Juli 2012 um 16:41 schrieben Sie:

> Thanks Thorsten and Ryan.

Please send your mail to the list again, you had a spelling error.

> 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.

And you are sure to connect to the proper repo? In your first mail
where you posted your configuration there was another realm configured
than the one you are getting on your login attempts.

Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning       E-Mail:Thorsten.Schoening_at_AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
Telefon.............030-2 1001-310
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hanover HRB 207 694 - Geschäftsführer: Andreas Muchow
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.