[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 1.5 clients can't authenticate to 1.4.6 Server

From: dan <danwalkeriv_at_gmail.com>
Date: Thu, 30 Oct 2008 00:46:25 -0600

I read that about the compatibility of 1.x clients and servers, which
is just another reason why this issue has been so confusing. This is
what a typical transaction looks like where the authentication fails.
The user is prompted to enter his/her password, even though their
credentials are stored and this wasn't necessary in the past. After
three attempts, the authorization failed message is displayed.

$ svn update
Authentication realm: <http://hostname.com:80> Subversion
Password for 'username': *********
Authentication realm: <http://hostname.com:80> Subversion
Username: username
Password for 'username': *********
Authentication realm: <http://hostname.com:80> Subversion
Username: username
Password for 'username': *********
svn: OPTIONS of 'http://hostname.com/subversion/repo': authorization
failed (http://hostname.com)

Thanks again for the help.

--dan

On Wed, Oct 29, 2008 at 6:48 PM, Ryan Schmidt
<subversion-2008c_at_ryandesign.com> wrote:
>
> On Oct 29, 2008, at 12:49, dan wrote:
>
>> We've been using Subversion for a while now in our lab with the following
>> setup:
>>
>> The server is an Ubuntu Hardy machine with the standard Subversion
>> 1.4.6 installed, which is accessed through apache. We are using
>> digest authentication.
>>
>> Here is the relevant portion of our apache.conf file:
>>
>> <Location /subversion >
>> Order allow,deny
>> Allow from all
>> DAV svn
>> SVNParentPath /home/subversion
>>
>> AuthzSVNAccessFile /home/subversion/svn.auth
>> AuthType Digest
>> AuthName "Subversion"
>> AuthDigestProvider file
>> AuthUserFile /home/webauth/webauth.password
>> AuthDigestDomain /webauth
>> Require valid-user
>> </Location>
>>
>> Recently, people have been updating to 1.5 clients, and we are finding
>> that they can no longer authenticate in order to commit. Is this a
>> known problem? Do we need to update the configuration in some way?
>
> According to the release notes, and general Subversion policy, any 1.x
> client should be able to connect to any 1.x server. What error message are
> your clients encountering?
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-31 23:20:18 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.