WORKAROUND2: Keep VisualSVN Server running under Network Service and use psexec tool to accept the certificate under Network Service account:
#Checkout a repository visualsvn server windows#
WORKAROUND1: Configure VisualSVN Server to run under a custom dedicated user account, login to Windows under this account, run svn.exe against the repository and permanently accept the untrusted certificate. buy the certificate) or sign server's certificate with Active Directory Certificate Services installed in your organization. You can obtain one from a certificate authority (i.e. SOLUTION: Run VisualSVN Server with a trusted signed server certificate.
So there is 1 correct solution to this and 2 workarounds: You can't logon under Network Service account as you usually logon under your user account but there is a smart trick which can help. As far as I guess your VisualSVN Server instance runs under Network Service account, so you have to login under Network Service, run svn.exe against the repository and permanently accept the certificate. VisualSVN Server runs under Network Service account, by default. Hooks are executed under the account which runs VisualSVN Server's service. Normally, you must manually accept such certificate on client-side.
You run VisualSVN Server with a self-signed certificate which is not trusted in your environment. The particular issue you've encountered is the side-effect of these facts: Common hook troubleshooting steps are described at the official Subversion FAQ: "Why aren't my repository hooks working?".
0 kommentar(er)
