Installing Trusted Certificates?

jezz.santos's Avatar


14 Jan, 2015 07:19 AM

Our build is running just fine at the moment, and MSTEST unit test are running just fine.
Now its time to run our integration tests. We have both web service integration tests and Protractor UI tests to run.
We have many web applications/services, and they all run on Windows Azure. Many of them call each other over HTTP/HTTPS.

On the desktop, when we run the integration tests they automatically spawn up the azure emulator, deploy the web apps and then run the tests. We have all this automated in the tests themselves by calling csrun.exe. And it all works just fine in our desktop environments.

One last thing. Many of our web apps use HTTPS instead of HTTP. And in order for them to call each other over HTTPS in the tests we need to use self-signed certificates, AND these certificates must be trusted by the local machine. (They must exist in the 'Trusted' certificate store). We dont yet have that part automated.

It seems like others have had success running integration tests using the 'Unstable' environment, so we will try that also, but how can we trust our certifcates?

Do we simply need to run a PS script on 'install' or 'init' to do that?
Will we have the relevant permissions to do that on the 'Unstable' environment?

  1. Support Staff 1 Posted by Feodor Fitsner on 14 Jan, 2015 05:37 PM

    Feodor Fitsner's Avatar

    You could import those certificates during the build using PowerShell:

    Build agent works under account in "Administrators" group so permissions is not a problem.

    Let me know if you have any questions.

  2. 2 Posted by jezz.santos on 14 Jan, 2015 06:58 PM

    jezz.santos's Avatar

    thanks, that is what I needed to confirm

  3. jezz.santos closed this discussion on 01 Feb, 2015 04:57 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac