Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

A unique secret key must be shared between all parts of the SonarQube infrastructure (server and analyzers). To generate it, go to Settings > Configuration > General Settings > Security > Encryption and click on Generate secret key:

2. Store the secret key on the SonarQube server

...

3. Generate the encrypted values of your settings

Go back to Settings > Configuration > General Settings > Security > Encryption and generate the encrypted values of your settings:

...

Restart your SonarQube server.

...

Analyzer side

Copy the secret key file to the machine running the analysis.

...

The sonar.password property is only encryptable since SonarQube 3.7.
Code Block
titlesettings.xml
languagehtml/xml
...
<profile>
  <id>sonar</id>
  <properties>
    <sonar.jdbc.url>jdbc:oracle:thin:@172.16.199.130/XE</sonar.jdbc.url>
    <sonar.jdbc.username>sonar</sonar.jdbc.username>
    <sonar.jdbc.password>{aes}CCGCFg4Xpm6r+PiJb1Swfg==</sonar.jdbc.password>
    ...
    <sonar.secretKeyPath>C:/path/to/my/secure/location/my_secret_key.txt</sonar.secretKeyPath>
  </properties>
</profile>
...
Note

 

 

Note

Note also that the Maven encryption mechanism can be used to encrypt password properties since SonarQube 4.3.