This an an archived version of the documentation for SonarQube version 4.5 & 4.5.x LTS.
See https://docs.sonarqube.org/display/SONAR/Documentation for current functionality
Your browser does not support iframes.
Description / Features
This plugin enables the delegation of SonarQube authentication to Atlassian Crowd.
Only password-checking is done against the external system. Authorization (access control) is still fully managed in SonarQube. That’s why Crowd users do not automatically have access to SonarQube. During the first authentication trial, if the password is correct, the SonarQube database is automatically populated with the new user. The System administrator should also assign the user to the desired groups in order to grant him necessary rights. If one exists, the password in the SonarQube account will be ignored as the external system password will override it.
2.0.2 - 2.2.x
- Install the plugin through the Update Center or download it into the SONARQUBE_HOME/extensions/plugins directory
- Restart the SonarQube server
- Make sure that at least one user with System administration role exists in SonarQube as well as in the external system
Update the SONARQUBE_HOME/conf/sonar.properties file by adding the following lines:
Restart the SonarQube server and check the log file for:
- Log in to SonarQube
Since SonarQube 4.2, technical users can be set. Technical users are authenticated against SonarQube's own database of users, rather than against any external tool (LDAP, Active Directory, Crowd, etc.).
Similarly, all accounts not flagged as local will be authenticated only against the external tool. By default
admin is a technical account. Technical accounts are configured in SONARQUBE_HOME/conf/sonar.properties in the
sonar.security.localUsers (default value = admin) property as a comma-separated list.
For versions prior to SonarQube 4.1, you can enable debug logging by adding the following to conf/logback.xml: