The configuration is pretty standard. The information to access the certificate must be provided in the configuration of the web server. JVMs used by the analyzers (SonarQube Runner, Maven, etc.) must know of the certificate.You'll find below a complete example: from the generation of an SSL Certificate to the configuration of the SonarQube web server and analyzers.
Here's a simple example:
Generating the SSL Certificate
Restart the web server. You should now only be able to access the SonarQube server over HTTPS on port 8999.
Configuring the Analyzers
From your browser, export the certificate into a file. Example with Chrome:
Click on Certificate information link and copy the certificate through the Details tab.
Add the certificate to the keystore of the JVM (that will be used by your analyzer) by running the following command:
keytool -import -alias sonartomcat -file <path_to_your_certificate> -keystore <path_to_cacert_of_JVM>
Running an Analysis
Update the settings of your analyzer (SONARQUBE_HOME/conf/sonar-runner.properties for SonarQube Runner or settings.xml for Maven...): sonar sonar.host.url=https://localhost:8999
Analyze one of your projects to check that it works fine.