Sonarqube 5.2 SQLServer Connection

Since Sonarqube 5.2 is released, the jTDS JDBC driver is no longer supported. We used this driver to connect to our instance of SQLServer, but we will have to switch to the Microsoft SQLServer driver. We run Sonarqube on Ubuntu and use an Active Directory account to connect to the SQLServer database. Since we work on Ubuntu, we cannot use integrated security, so credentials must be provided in the JDBC configuration for Sonarqube. This will result in the following properties:

sonar.jdbc.url=jdbc:sqlserver://sqlserverhost.my.domain.com:1433;databaseName=sonar;selectMethod=cursor
sonar.jdbc.username=someuser
sonar.jdbc.password=somepassword

This leads to the fact that SQLServer appears in the "Login Error" with the message "Could not find the login that matches the specified name."

The next thing I tried is a connection with a username containing a domain, resulting in the following properties:

sonar.jdbc.url=jdbc:sqlserver://sqlserverhost.my.domain.com:1433;databaseName=sonar;selectMethod=cursor
sonar.jdbc.username=DOMAIN\\someuser
sonar.jdbc.password=somepassword

This also results in "SQLServer login error", the message "Attempting to use the NT account name with SQL Server authentication" appears here.

What am I missing?

UPDATE:
Sonarqube magazine can be found here: http://pastebin.com/AGB9bTQG
I can think of one thing that is different from the jTDS connection url: The jTDS connection url contains "; domain = my.domain.com", which does not appear to support the Microsoft SQLServer driver. So I tried installing DOMAIN \ someuser, which SQLServer failed.

+4
4

. : 1443 selectMethod

sonar.jdbc.url = JDBC: SQLServer://sqlserverhost.my.domain.com; DATABASENAME =

0

:

sonar.jbc.url = jdbc: sqlserver://{server}: {port #}; databaseName = {db name}

.

sonar.jbc.url = JDBC: SQLServer://: 36549; DATABASENAME =

SQL Server, TCP/IP , SQL, . , , SSMS.

SQL Server TCP / IP Settings

Re: Windows Auth to SQL Server - SQL Server Auth, sonar.jdbc.username sonar.jdbc.password, SonarQube , SonarQube; , .

0
source

Our solution was to create a SQL Server account with access rights to the database and use it instead of using the AD / Windows account.

-1
source

Source: https://habr.com/ru/post/1614571/


All Articles