Have you updated to version 1.6.1? It resolved some issues with inherited permissions.
Carey On Thu, Oct 23, 2008 at 11:01 AM, adam.c.main <[EMAIL PROTECTED]> wrote: > > Carey, > > I'm using the VisualSVN Server Management console to add my AD groups > and invidual users. > > My authz-windows is as follows: > > [/] > S-1-5-32-545=r > > [Test:/] > S-1-5-21-3863570177-2765681283-2415621057-9658=rw > > Even though the user is in the group specified for Test, they only > have readonly access for that repository that is granted by Builtin > \Users on the root. > > If I add a user specifically, I get: > > [/] > S-1-5-32-545=r > > [Test:/] > S-1-5-21-3863570177-2765681283-2415621057-9658=rw > S-1-5-21-3863570177-2765681283-2415621057-9756=rw > > The user can now update and commit like normal in Test. > > -Adam > > Carey Bishop wrote: >> Hi Adam, >> >> VisualSVN Server 1.6.x uses a different method to store Windows user >> permission data than the normal authz or passwd files. If you have >> previously been using SVNServe, then switch to using VisualSVN Server >> with Windows authentication, it will not import the current >> permissions you have specified in your passwd file, you will need to >> recreate them using the VisualSVN Server Management console. >> >> A message to this effect pops up during the installation of VisualSVN Server. >> >> Carey >> >
