> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/10.7/instance-administration/authentication/http-header.md).

# HTTP header

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

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.

![](https://3272878703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI10pmJWeVVXYITlQJllp%2Fuploads%2Fgit-blob-cf613ec4030d22bbd004f621ba94723058de47cc%2F427aabec883bfd25b61b383cc6ca0fc598450279.png?alt=media)

All the parameters required to activate and configure this feature are available in the 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 deployment with an in-house SSO implementation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-server/10.7/instance-administration/authentication/http-header.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.