Hi all,
We are looking to use Sonarqube in our organisation and we have been looking at ways to "hide" the password from users so that they can't access the DB.
We've been looking at:
where you can use a key to create an encrypted version, paste it in and then it's hidden.
We are looking at using some automated tool (such as puppet) create the instance, so would it would to would be
create all the sonar files
go somewhere for the "clear" DB password
paste the password into "sonar.jdbc.password"
then start sonarqube.
when sonarqube starts, it can see that there is a "sonar.secretKeyPath" setup, and if there is and the password is in cleartext it will encrypt the password and write back the change to the "conf/sonar/properties" file.
this means that if we want to roll passwords, we can update the password and restart the sonar server and it will re-encrypt the new password.
Does this sound reasonable and is there a better approach ?
Our other option is we just run some java code after we have installed sonar and try to call out to the sonar libraries to encrypt the password and do it outside of sonar.
Regards
Richard