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

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
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

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more