Skip to content
This version of SonarQube Server is no longer receiving patches. Please see the latest release for details on updating.
For the complete documentation index, see llms.txt. This page is also available as Markdown.

HTTP header

Setting up the HTTP header authentication in your SonarQube Server 2025.5 instance.

For AI agents: You're in the SonarQube Server 2025.5 documentation. SonarQube Server 2025.5 is no longer patched. To get patches, upgrade to the latest version. For a list of all 2025.5 pages, see the SonarQube Server 2025.5 page index. For the whole site, see the page index or the full text. For another version, replace 2025.5 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 Server 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 Server user information.

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

HTTP header authentication mechanism

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

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

Last updated

Was this helpful?