Hello Bryan, > Thank You for the information and the links, I will look into your > suggestions.
I now recall another workaround that you might find helpful. You can disable password caching on the client completely. This way your u sers will be required to enter their credential every time the access Subversion repositories and a reviewer will be prompted to enter his credentials. You can disable client credentials caching via modifying client's runtime configuration. For example, edit "servers" file on the machine where. The file is located in "%APPDATA%\Subversion" directory on Windows. Just put the following string to the [Global] section of the "servers" file: [[ store-passwords = no ]] Please note that on Windows, Subversion can use Windows Registry to store configuration data, so you can apply configuration changes via a Group Policy that modifies registry for selected Active Directory users. This approach does not require you to manually edit each user's runtime config. For further details regarding Subversion configuration options consider the Runtime Configuration Area chapter in the Version Control with Subversion book at https://www.visualsvn.com/support/svnbook/advanced/confarea/. -- 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.
