diff options
| author | kevin-hinz <kevin.hinz@sonarsource.com> | 2022-10-06 10:05:41 +0200 |
|---|---|---|
| committer | sonartech <sonartech@sonarsource.com> | 2022-10-11 20:03:59 +0000 |
| commit | 526a6d339a6ba456486bd288c792416fe56973c5 (patch) | |
| tree | e8c8d770d8c20f6d7e72e3d7ce4ddac0ab8cd868 /server/sonar-docs/src/pages/setup | |
| parent | 56884c45a276d804ff0aba9eb7e2c7fc417cf1bb (diff) | |
| download | sonarqube-526a6d339a6ba456486bd288c792416fe56973c5.tar.gz sonarqube-526a6d339a6ba456486bd288c792416fe56973c5.zip | |
DOC-160, integrate 9.6 Release notes
Diffstat (limited to 'server/sonar-docs/src/pages/setup')
| -rw-r--r-- | server/sonar-docs/src/pages/setup/install-server.md | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/server/sonar-docs/src/pages/setup/install-server.md b/server/sonar-docs/src/pages/setup/install-server.md index e0f48f5c21c..5a70208e21e 100644 --- a/server/sonar-docs/src/pages/setup/install-server.md +++ b/server/sonar-docs/src/pages/setup/install-server.md @@ -53,15 +53,21 @@ Create an empty schema and a `sonarqube` user. Grant this `sonarqube` user permi |``` |ALTER DATABASE YourSonarQubeDatabase SET READ_COMMITTED_SNAPSHOT ON WITH ROLLBACK IMMEDIATE; |``` +|### Encryption +| +|_If your Microsoft SQL Server doesn't support encryption_, you must add `encrypt=false` to the JDBC URL connection string. +| +|_If your Microsoft SQL Server requires encryption but_ you don't want SonarQube to validate the certificate, you must add `trustServerCertificate=true` to the JDBC URL connection string. +| |### Integrated Security | |To use integrated security: | |1. Download the [Microsoft SQL JDBC Auth 11.2.0 package](https://github.com/microsoft/mssql-jdbc/releases/download/v11.2.0/mssql-jdbc_auth.zip) and copy `mssql-jdbc_auth-11.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. +|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. +| _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. | |