SSL Error causing Cruise Control Issue

rifferte · Post by **rifferte** » Tue Aug 03, 2004 12:22 pm

I am trying to get CruiseControl.Net(ccnet) set up for my dev team and I have run into and issue with Vault.

CCnet attempts to run the history command on our reposistory - which works but brings up an error before the XML like output:

Certificate Problem with accessing https://myvaultserver/VaultService/VaultService.asmx
Problem code 0x00000000, Unknown Certificate Problem.
Accepting Certificate despite problems.

This is causing an issue with CCnet becuase it is expecting XML so it can parse out the history. If I connect without SSL - the issue goes away.

I brought this issue up awhile back concerning the GUI for this error - but that way before I attempted to use Vault from CCnet.

So - my questions are:
1) Can the error be resolved (or is this a .Net Framework issue)
2) Is there a way to suppress the error message?
3) Could the error at least be surrounded by some tags so that the file is still XML like?

Thanks,

Ron

Guest · Post by **Guest** » Tue Aug 03, 2004 12:29 pm

If it helps = I am using Vault 2.03.

Post by **jclausius** » Wed Aug 04, 2004 1:30 pm

There's nothing that can be done at this moment. I'll log a feature request to re-work the xml output, so extra information is included within xml.

rifferte · Post by **rifferte** » Sun Aug 08, 2004 8:30 pm

Thanks for the info - I think that will help out all of us using an external process on the history command.

adakin · Post by **adakin** » Fri Sep 17, 2004 3:27 pm

Any update on this? I'm using 2.06 and it's making FinalBuilder not work.

There is definatley nothing wrong with this SSL cert...

dan · Post by **dan** » Mon Sep 20, 2004 9:34 am

We will look into it, but I can't promise whether this particular issue can be solved - it depends where the error message is coming from. If it is coming from the .Net framework, we wouldn't be able to wrap it in our xml.

In any case, you might try bring up the GUI client for the same user on the same machine, and accepting the certifcate to the server you are connecting to. It should not ask again after that, and then you shouldn't get this particular error anymore.

Let us know whether that solves the problem.

Thanks,

adakin · Post by **adakin** » Mon Sep 20, 2004 10:12 am

It's been accepted in the client GUI already. You never see this error in the client GUI after that first time accepting the cert.

Running the commandline version you see the error every time a command is run.

I emailed a friend about it who also runs Vault with SSL and who has a Verisign cert. He hadn't tried the commandline version yet, but when he did he got the same problem.

My cert is a Thawte cert.

Just to test things I setup our copy of Vault in one of our webs with a GeoTrust cert and it had the same thing also.

What certs does this thing work with? Between Verisign, Thawte, and Geotrust that pretty much covers the bases. Also our Thawte and Geotrust certs are being used for other sites and never have a problem.

Post by **jeremy_sg** » Mon Sep 20, 2004 1:03 pm

I'll get this fixed in version 2.1.

sethgray · Post by **sethgray** » Tue Nov 09, 2004 1:48 pm

We've been effectively unable to automate a build process with our offshore development team because of this error. We cannot send our source code over the wire without SSL. Any ideas? work arounds?

The workflow is pretty ugly and leads to occasional (maybe more frequent than occasional) user error on the upload process.

Post by **jeremy_sg** » Tue Nov 09, 2004 2:19 pm

Vault 3.0 will have this fixed. We expect a release in the next couple of weeks.

SourceGear Support

SSL Error causing Cruise Control Issue

SSL Error causing Cruise Control Issue

Any update to the status of this?