Skip to main content

SonarQube–Connecting to an on-premise Azure DevOps failed

After successfully installing a new SonarQube server, I followed the documented steps to configure the Azure DevOps integration. However when trying to register our on premise Azure DevOps instance, SonarQube throwed the following exception:

2025.02.10 11:47:30 ERROR web[13308e38-2d1a-46ae-80d9-baa54c12ffac][o.s.a.c.a.AzureDevOpsHttpClient] Unable to contact Azure DevOps server for request [https://azuredevops.server.be/tfs/defaultcollection/_apis/projects?api-version=3.0]: [PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

I found an old post online that links this error message to a problem with our SSL certificate. It seems that Java is unable to recognize the root certificate authority (CA). This could make sense as our internal Azure DevOps instance is using an SSL certificate signed by an internal root certificate.

To fix the issue, I followed the steps described in the post:

  • First I exported the existing keystore to a file using the following command:

keytool -list -v -keystore "C:\Program Files\Microsoft\jdk-17.0.11.9-hotspot\lib\security\cacerts"  > java_cacerts.txt

  • I checked the exported file and indeed the root certificate was missing. So we need to add it to our keystore.
  • I already had the root certificate available as a .cer file so I could import it immediately:

keytool -import -alias VLM_ROOT -keystore "C:\Program Files\Microsoft\jdk-17.0.11.9-hotspot\lib\security\cacerts"  -file rootcert.cer

Enter keystore password:

Owner: CN=Enterprise Root CA 1, DC=server, DC=be

Issuer: CN=Enterprise Root CA 1, DC=server, DC=be

Serial number: 536c46e9d58b64a14005e8e460f5a834

Valid from: Mon Nov 08 08:08:22 CET 2021 until: Sat Nov 08 08:15:58 CET 2036

Certificate fingerprints:

Signature algorithm name: SHA256withRSA

Subject Public Key Algorithm: 2048-bit RSA key

Version: 3

  • I had to confirm that I trusted this certificate:

Trust this certificate? [no]:  Y

Certificate was added to keystore

After doing that I was able to create the connection between SonarQube and Azure DevOps without any other issues.

More information

SonarQube on Windows Troubleshooting

PKIX path building failed: SunCertPathBuilderException: unable to find valid certification path to requested target

Azure DevOps integration | SonarQube Server Documentation

Labels:

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...
Read more

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.
Read more

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...
Read more