Just as a FYI: the issue Rob is referring to is the (in)famous issue
3242 - "Subversion demands unnecessary access to parent directories of
operations"
See http://subversion.tigris.org/issues/show_bug.cgi?id=3242
It's a long standing issue, but if I understood correctly a fix is in
progress ...
On Jan 9, 2010, at 12:58 PM, Rob van Oostrum wrote:
> 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]
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 ba
Thanks, but that is incorrect. I have no problem downloading sources with a
single rule of "[/project] *=r", nor do I have a problem correctly resolving
group memberships that a user has assigned to them. As well, I have tested
that a user who is not logged in cannot access the repository.
Ar
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
f
Hello all,
I've been wrestling with getting authz setup in a way that must be somewhat
unconventional all week and was hoping someone here on the list might be able
to offer some insight. The environment is Apache httpd 2.2.3, mod_dav_svn
1.6.6, and Subversion 1.6.6. My configs follow.
So fa
