HTTP header

In SonarQube 10.0, you can delegate user authentication to third-party systems (proxies/servers) using HTTP header authentication.

For AI agents: You're in the SonarQube Server 10.0 documentation. For a list of all 10.0 pages, see the SonarQube Server 10.0 page index. For the whole site, see the page index or the full text. For another version, replace 10.0 in the URL with that version. The latest version has no version number in its URL.

You can delegate user authentication to third-party systems (proxies/servers) using HTTP header authentication.

When this feature is activated, SonarQube expects that the authentication is handled prior to any query reaching the server. The tool that handles the authentication should:

• Intercept calls to the SonarQube server.

• Take care of the authentication.

• Update the HTTP request header with the relevant SonarQube user information.

• Re-route the request to SonarQube with the appropriate header information.

All the parameters required to activate and configure this feature are available in the SonarQube server configuration file. See the SSO AUTHENTICATION section in <SONARQUBE_HOME>/conf/sonar.properties.

Using HTTP header authentication is an easy way to integrate your SonarQube deployment with an in-house SSO implementation.