# HTTP header

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.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/j4cKRv7AziRE3QTKnOpA" alt="HTTP header authentication mechanism"><figcaption></figcaption></figure>

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.


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

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

The question should be specific, self-contained, and written in natural language.
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.