Skip to main content

TFS Build Agent - SSL certificate problem: unable to get local issuer certificate–Part 2

Note: This is a continuation of a previous post found here: https://bartwullems.blogspot.com/2018/06/tfs-build-agent-ssl-certificate-problem.html

In the previous post I suggested a solution which disables the SSL verification check. Of course, this is more a dirty heck and not a great solution at all. Let’s have a look at a better solution:

Step 1  - Extract the root certificate

Browse to your TFS portal. Inside the browser go to the SSL certificate(exact steps can differ depending on your browser of choice; here are the steps for Chrome: https://bartwullems.blogspot.com/2017/05/how-can-i-view-used-ssl-certificate-in.html)

image

Once you have the certificate window open, go to the Certification Path tab and select the top-most certificate in the chain.

image

Click View Certificate, go to the Details tab and click on the Copy to File… button.

image

The export wizard will be started start the export wizard for certificates. On the second page of the wizard, you will be asked what format to use for exporting your certificate. Choose the second option: base64 encoded X.509.

image

Click Next, specify a file name and save the certificate to disk.

Step 2 – Create a copy of the Git certificate store

Browse to the location of the git certificate store(on my machine this is C:\Program Files\Git\usr\ssl\certs). Copy the ca-bundle.crt to your user profile directory (%USERPROFILE%) alongside your user .gitconfig file.

Step 3 – Add the root certificate to the Git certificate store

Open the exported certificate, copy its entire content to the clipboard. Afterwards open the copy of the ca-bundle.crt file and paste the exported certificate content to the end of this file.

image

Step 4 – Configure git to use the Git certificate store copy

Execute the following command to point git to your private copy of the certificate store:

git config --global http.sslCAInfo C:/Users/yourname/ca-bundle.crt

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...