Unable to access our SVN server using SVN 1.8 client

Hi, we're serving a svn repository using Debian 7 and mod_dav_svn.so in apache: Apache/2.2.22 (Debian) DAV/2 SVN/1.6.17 PHP/5.4.4-14+deb7u7 We want to have all members of a certain ldap-group to have full access. Furthermore, some users from the ldap-directory not in that group shall have access

Re: Unable to access our SVN server using SVN 1.8 client

What error do you see in TortoiseSVN or other 1.8 clients? Subversion 1.8 will look at parent directories to find inherited properties, but it will just ignore properties on directories which it can't read. Bert Sent from Windows Mail From: Johannes Michler Sent: ‎Saturday‎,

Re: Unable to access our SVN server using SVN 1.8 client

Hi Bert, well the client is asking over and over again and finally gives up: C:\Users\jmichler\Desktop\test>svn co https://SERVER/svn/PROJEKTE/KUNDE1/trunk/R12/ Authentication realm: PROMATIS Authentifizierung Password for 'user1': Authentication realm:

Re: Unable to access our SVN server using SVN 1.8 client

On 2/25/14, 11:04 AM, Johannes Michler wrote: > well the client is asking over and over again and finally gives up: > C:\Users\jmichler\Desktop\test>svn co > https://SERVER/svn/PROJEKTE/KUNDE1/trunk/R12/ > Authentication realm: PROMATIS Authentifizierung > Password for 'user1'

Re: Unable to access our SVN server using SVN 1.8 client

Hi Ben, well I'm using Apache 2.2: apache2 -v Server version: Apache/2.2.22 (Debian) Server built: Jan 31 2014 18:55:37 Is there a workaround for 2.2 as well? Regards, Johannes 2014-02-25 20:36 GMT+01:00 Ben Reser : > On 2/25/14, 11:04 AM, Johannes Michler wrote: > > well the client is ask

Re: Unable to access our SVN server using SVN 1.8 client

On 2/25/14, 11:44 AM, Johannes Michler wrote: > well I'm using Apache 2.2: > apache2 -v > Server version: Apache/2.2.22 (Debian) > Server built: Jan 31 2014 18:55:37 > > Is there a workaround for 2.2 as well? Yeah just realized that looking at your original mail. 2.2 shouldn't have that behavi

Re: Unable to access our SVN server using SVN 1.8 client

Well but by looking into my logfiles I see that my server is indeed sending HTTP-401. Is this the problem? Regards, Johannes 2014-02-25 20:51 GMT+01:00 Ben Reser : > On 2/25/14, 11:44 AM, Johannes Michler wrote: > > well I'm using Apache 2.2: > > apache2 -v > > Server version: Apache/2.2.22 (De

Re: Unable to access our SVN server using SVN 1.8 client

On 2/25/14, 12:03 PM, Johannes Michler wrote: > Well but by looking into my logfiles I see that my server is indeed sending > HTTP-401. Is this the problem? I don't think there's really anything that a 1.8 client can or should do different here. The server is saying "give me authn credentials" an

AW: Unable to access our SVN server using SVN 1.8 client

Hi, Ben, Von: Ben Reser [mailto:b...@reser.org] > > On 2/25/14, 12:03 PM, Johannes Michler wrote: > > Well but by looking into my logfiles I see that my server is indeed > > sending HTTP-401. Is this the problem? > > I don't think there's really anything that a 1.8 client can or should do > diff

Re: Unable to access our SVN server using SVN 1.8 client

On 2/25/14, 12:52 PM, Ben Reser wrote: > 2) Write a custom authz hook that always returns HTTP_FORBIDDEN that hooks > after the ldap module. Configure your custom module to be turned on for your > location. Then set 'AuthzLDAPAuthoritative off', meaning that the ldap module > will DECLINE and the

Re: Unable to access our SVN server using SVN 1.8 client

On 2/25/14, 3:37 PM, Ben Reser wrote: > Both mod_authz_default and mod_authz_forbid are registering in the > APR_HOOK_LAST group. So their order is not determinate. If you want to avoid > mod_authz_forbid activating for any other traffic (with or without > mod_authz_default) loaded you should add

Re: AW: Unable to access our SVN server using SVN 1.8 client

On 2/25/14, 1:25 PM, Markus Schaber wrote: > I tend to think it might be a sensible behavior to not prompt for > Authentication on the client side during specifically this kind of > upwards tree walk when the client successfully authenticated for the > "main" request, and later fails with the sam

Fwd: AW: Unable to access our SVN server using SVN 1.8 client

I accidentally responded only to Ben: On 2/25/14, 7:37 PM, Nico Kadel-Garcia wrote: > And, sometimes, it just gets more reliable to use svn+ssh and avoid > the entire Apache infrastructure complexity. There are so *many* > variants of authentication, and filesystem and multi-platform feature > in