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

Re: Restrict Read Access at Branch Level

From: p karthik <karthik1212_at_gmail.com>
Date: 2007-09-02 20:14:14 CEST

Hi All,

The per-directory access control is working fine now using the svn-acl file.
But now I have a different problem.

I have around 20 branches on which I need to impose read restriction.
For that I have explictly written the name of the branch and then gave no
permission to the group.

Is there any way that I can minimize this explicit mentioning of the name by
any means like a regular expression?
I need this because I need to restrict the same group of people if I am
creating a new branch. And this creation is very frequent as we are
following agile methodology and I need to add each entry in the svn-acl file
when ever I create the branch.

Thanks in anticipation.
Karthik.

On 8/30/07, p karthik <karthik1212@gmail.com> wrote:
>
> Hi Hari/Ranier,
>
> Thanks a ton for your inputs.
>
> Yes Ranier, the files have read permissions for other users.
>
> Hari,
>
> As you suggested I have tried with the basic authentication, Require
> valid-user and then AuthzSVNAccessFile. The httpd.conf has the entry as:
>
>
>
> <Location /dummy>
> DAV svn
> SVNPath /subversion/dummy
> SVNReposName "NEO Dummy Repository"
> AuthType Basic
> AuthName "Subversion repository"
> AuthzSVNAccessFile /workarea/svn/svn-acl
> AuthUserFile /export/home/svn/svn-auth-file
> Require valid-user
> </Location>
>
> The contents of svn-acl file are as follows:
> [dummy:/]
> karthikp = wr
> dummy = r
> admin = wr
> [dummy:/core/branches/core_final_bugfix]
> karthikp = r
> dummy =
> admin = wr
>
> It seems to work now. I think I need to remove the pre-commit hook script
> which I have written in PERL if this comes in to picture.
>
> But I have a query regarding this. Can I have the list of users in a file
> and reference that so that I can only change that file instead of changing
> the svn-acl file?
>
> Thanks a lot once again.
>
> Karthik.
>
>
> On 8/30/07, Hari Kodungallur <hkodungallur@gmail.com > wrote:
> >
> >
> >
> > On 8/30/07, p karthik <karthik1212@gmail.com > wrote:
> > >
> > > Hi Hari/All,
> > >
> > > I have noticied "access denied" message in the error log of apache.
> > >
> > > [Thu Aug 30 16:50:07 2007] [error] [client <IP>] Access denied: -
> > > REPORT dummy:/
> > >
> > > This shows that I am not configuring properly my httpd.conffile/svn-acl file.
> > > Please help me in this regard.
> > >
> > >
> >
> > In this case, it looks like it is because you have limited the access to
> > POST, PUT, GET and PROPFIND. You should also have one for REPORT and OPTIONS
> > (they can be grouped with GET and PROPFIND).
> >
> > There can be other reasons for 403 -- incorrect password, incorrect
> > configuration file that results in apache not knowing about the access etc.
> > If the issue persists, my suggestion will be to start off with very basic
> > authentication for everyone and then add the userfile, then the groupfile
> > etc. If you have everything in place and if you get the error, any one of
> > them could be the problem. So, try doing it one step at a time.
> >
> > Hope this helps.
> >
> > regards,
> > -Hari Kodungallur
> >
> >
> >
> >
>
Received on Sun Sep 2 20:11:30 2007

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.