Hello Bryan, > I recently upgraded our old SVN system up to a WIndows Server using > VisualSVN Server 3.3.1. > I ported over all of the projects successfully and added all of the users > and as needed. > > On our previous system, whenever a user tried to commit items they did not > have permission > to commit, TortoiseSVN would ask for a new login to allow someone who Does > have access to commit > thier files after checking them. > > Under the new system when someone tries to commit without access, I only get > a 403 Forbidden Error, > with no new login asked for. > > What settings am I missing that will have the system ask for new Credantials > when the existing login > does not have write permissions?
I suggest following these steps: * Clear Subversion credentials cache. For example, you can do this via TortoiseSVN | Settings | Saved data | Clear all. * Make sure that you've configured access rules on your repositories: 1. Start VisualSVN Server Manager, 2. Expand "Repositories". 3. Right-click a repository and select Properties, 4. Verify that there all required access rules are in place. -- With best regards, Pavel Lyalyakin VisualSVN Team -- You received this message because you are subscribed to the Google Groups "VisualSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to visualsvn+unsubscr...@googlegroups.com. To post to this group, send email to visualsvn@googlegroups.com. Visit this group at http://groups.google.com/group/visualsvn. For more options, visit https://groups.google.com/d/optout.
