Advanced configuration

Sometimes network infrastructures require custom setups to let SonarQube for IDE perform HTTP requests. These properties will help make this happen.

HTTP configuration

To operate, SonarQube for Visual Studio needs to perform HTTP requests, especially in Connected mode. While SonarQube for Visual Studio will work out-of-the-box in most situations, some network infrastructure may require a custom configuration.

Proxy configuration

When connecting to a SonarQube instance running behind a proxy, SonarQube for Visual Studio will use the your Windows-defined proxy settings. See the Microsoft documentation for more information about setting up a proxy server connection.

Manage your configuration

Server SSL certificates

When encountering an untrusted certificate, SonarQube for Visual Studio will inform the user with a notification that the server certificate can not be verified.

SonarQube for Visual Studio will provide a gold bar notification if your certificate cannot be verified.

The truststore.p12 is expected to be found in the default location as listed below; add it manually if it doesn’t exist. Here is an example command that might work for your configuration:

keytool -import -trustcacerts -keystore ~/.sonarlint/ssl/truststore.p12 -storepass sonarlint -noprompt -file <YOUR_CERTIFICATE_NAME.cer>

TrustStore

sonarlint.ssl.trustStorePath

Path to the keystore used by SonarLint to store custom trusted server certificates

default: ~/.sonarlint/ssl/truststore.p12

sonarlint.ssl.trustStorePassword

Password of the truststore.

default: sonarlint

sonarlint.ssl.trustStoreType

The format of the keystore file is found in the Oracle documentation.

default: PKCS12

If you're having troubles connecting to the server due to SSL/TLS errors, see the SSL/TLS errors troubleshooting article.