Apache is used only to authorize the remote user accessing the repository
via Internet. In the case of local user access to repository, Apache is not
coming in picture. To authorize the local user request, subversion supports
the templetes for hook scripts which will only athorize the user request for
commit operations. If anyone knows how to implement the read and write
sentinels in Subversion then I think the local user request accessing for a
resource can be authorized by these read and write sentinels. Please keep in
mind that the protocol for implementing the read and write sentinels is yet
to be implemented.
----- Original Message -----
From: "Nitin Shukla" <nitinshukla@infotech.stph.net>
To: "'emf'" <i@mindlace.net>; <dev@subversion.tigris.org>
Sent: Thursday, December 26, 2002 12:59 PM
Subject: RE: How much libsvn_repos wrap around the libsvn_fs
> Nitin Shukla wrote:
> > Has there been any approach to develop the read hook scripts
> > I know that the read sentinels are yet to be implemented and
> > is supposed to communicate with the Subversion server using
> > protocol which not decided yet. Probably LDAP can be used
> > if we can make Subversion server understand LDAP protocols.
> > If anyone has thought any approach i.e. developing read hook
> > scripts and/or implementing the read sentinels pls. update me.
>
> ~mindlace wrote:
> I don't understand why you're trying to solve this problem in subversion;
it
> seems like the place to handle this is apache. Having per-path permissions
> checking would be relatively easy to implement with, for example,
mod_python
> (or
> mod_perl, if that's your preference) which could call out to LDAP or
> whatever
> external permission-storing mechanism you want to use.
>
> Apache can handle request for remote svn client. We can solve the problem
of
> Access
> Control with your approach. But how do we go about handling the local svn
> client
> requests? One approach seems to be the hook programs but currently they
are
> not
> sufficient hook programs to provide read, write control.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 26 10:30:17 2002