Volker Cordes wrote on Fri, Jan 13, 2017 at 18:47:17 +0100:
> Am 13.01.2017 um 15:47 schrieb Daniel Shahaf:
> > Volker Cordes wrote on Fri, Jan 13, 2017 at 10:51:19 +0100:
> >> Hello,
> >>
> >> I have set up path based authorization on a repository. If I check out
> >> the project, everything
Am 13.01.2017 um 15:47 schrieb Daniel Shahaf:
> Volker Cordes wrote on Fri, Jan 13, 2017 at 10:51:19 +0100:
>> Hello,
>>
>> I have set up path based authorization on a repository. If I check out
>> the project, everything works as expected. My problem however is, that
>> if I change permissions of
Volker Cordes wrote on Fri, Jan 13, 2017 at 10:51:19 +0100:
> Hello,
>
> I have set up path based authorization on a repository. If I check out
> the project, everything works as expected. My problem however is, that
> if I change permissions of a file / path and then update the working
> copy
Your problem is with Crowd, not authz. Authentication is failing: Could not
authenticate to server: rejected Basic challenge (https://dev.host.net)
Check your Crowd configuration/documentation. I'd suggest taking SVN out of
the equation and verifying that your integration with Crowd is working
I see now. The path /project/!svn makes no sense. It doesn't exist in the
repository, so that rule doesn't do anything. The !svn is a SVN-internal
concept. To assign permissions to /project, you need to have to specify:
[/project]
* = r
Do a search on the old list archives on tigris for some
