I'm trying to integrate SVN with BugTracker.NET. On the page that accesses SVN I get the error "Server certificate verification failed: certificate issued for a different hostname, issuer is not trusted". I'm using VisualSVN Server for the SVN server.
A:
Say you're trying to access
https://www.xyz.com/<whatever>
And the certificate has been issued to www.abc.com. Try
https://www.abc.com/<whatever>
And it should work.
Spencer Ruport
2009-08-19 18:16:34
It's true that the certificate was issue for the machine name and the client is using an external IP to access the machine, but even if I knew how to change the assigned name on the certificate, the client machine would not recognize it (I think). So I need to make the SVN client accept permanently the certificate for the ASPNET user.
Paulo Manuel Santos
2009-08-19 18:24:51
Hey, I finally see something, after I deceived the client machine by changing the hosts file and using the SVN server name to connect to the SVN. Then by adding the argument "--trust-server-cert" BugTracker.NET is able to access SVN. it still bothers me to change the hosts file, but if there is no better solution I'll have to accept this one! Thanks.
Paulo Manuel Santos
2009-08-19 18:46:34
+1
A:
I found the solution:
Open a cmd window on the bugtracker.net server. Write any svn command adding the svn option "--config-dir C:\whatever" Accept permanently the certificate.
The user files will be saved in the C:\whatever directory
Then go to the bugtracker.net web.config file and add the same option to the SubversionAdditional args. add key="SubversionAdditionalArgs" value="--config-dir c:\whatever"
And it will work fine forever since the IUSER_HOST windows user (ASP user) will use that cache directory and will find the file to trust the machine)
netzorro
2009-09-12 17:36:08