Certain groups at my organization will not or are not allowed to use basic authentication - both because passwords are generally cached/ saved on the client and unencrypted when using basic. So we have have 2 locations setup that point to the same repo set - one that uses the standard visualsvn auth-windows and one that uses sspi with basic disabled.
I suppose all things would be solved if sspi was offered as part of the standard visual svn server setup On Feb 13, 6:57 am, VisualSVN Support <supp...@visualsvn.com> wrote: > Steven, > > >I have access granted via the Visual > > SVN Server standard windows setup but also have to grant access via > SSPI for some groups - the SSPI access is using a standard authz file. > > Sorry for possible misunderstanding, but what for do you try to use > SSPI together with VisualSVN Server built-in authentication? > > You could use VisualSVN Server Manager to give the access rights for groups. > > Please could you clarify? > > Thank you! > > > > On Tue, Feb 10, 2009 at 9:07 PM, Steven <steven.be...@gmail.com> wrote: > > >> Please could you provide more details about the problem with using SIDs? > > >> Thank you! > > > Thanks, I'll check out using Everyone as a wildcard to deny access. > > > In terms of problems with SIDs, I have access granted via the Visual > > SVN Server standard windows setup but also have to grant access via > > SSPI for some groups - the SSPI access is using a standard authz file. > > I want it all managed from a single place though (The VisualSVN server > > gui), so my plan is to write a little .net script that will take the > > authz-windows file and convert it to a standard authz by looking up > > all the SIDs but it would be nicer (from my point of view) if I could > > have just a single, standard authz file. Thanks > > > Steven > > -- > Olga Dolidze > VisualSVN Support
