Skip to main content

SonarQube - SQL Server Integrated Security

While moving our build agents from one server to another, I also had to move our SonarQube instance.

To install the SonarQube instance I followed the instructions mentioned here: https://docs.sonarqube.org/latest/setup/install-server/

As I was using SQL Server with Integrated Security, I took special attention when reading this section:

To use integrated security:

  1. Download the Microsoft SQL JDBC Driver 9.2.0 package and copy mssql-jdbc_auth-9.2.0.x64.dll to any folder in your path.

  2. If you're running SonarQube as a Windows service, make sure the Windows account under which the service is running has permission to connect your SQL server. The account should have db_owner database role membership.

    If you're running the SonarQube server from a command prompt, the user under which the command prompt is running should have db_owner database role membership.

  3. Ensure that sonar.jdbc.username or sonar.jdbc.password properties are commented out or SonarQube will use SQL authentication.
sonar.jdbc.url=jdbc:sqlserver://localhost;databaseName=sonar;integratedSecurity=true
This instructions were not completely obvious to me. So here is some extra info in case you don’t get it working with the instructions above:
Tip 1: 
If you are looking for the mentioned dll, you can find it in the following folder inside the zip file: \enu\auth\x64\mssql-jdbc_auth-9.2.0.x64.dll 
Tip 2: 
It wasn’t clear to me what was meant with any folder in your path. I copied the DLL to both the bin and lib folder of my OpenJDK installation.
Tip 3:
After doing the steps above, it still didn’t work. Turns out that SonarQube was expecting the 9.2.0 version. If you follow the download link, you arrive at the latest version of the JDBC driver which is version 9.2.1.
To get the correct DLL, I had to go to Github and download the correct version there: https://github.com/microsoft/mssql-jdbc/releases/tag/v9.2.0
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