Skip to content
LogScale Self-Hosted
This is an archived version of the documentation downloaded from LogScale Documentation Archives. Up to date documentation, and documentation for later versions, is available on LogScale Documentation

## Authenticate with a proxy

LogScale supports single sign-on (SSO) authentication through a reverse proxy configuration, where the proxy provides user identity verification via HTTP headers. The setup requires proper configuration of authentication methods and header names, with critical security considerations around preventing direct server access and ensuring the proxy correctly manages user identity headers.

One way to accomplish single sign-on (SSO) in LogScale is by using a reverse proxy in front of LogScale. If that proxy has a way of knowing a proper username, user email, or other unique user identifier, you can let the proxy decide what username the user gets access as inside LogScale.

### Important

Make sure LogScale is not accessible without passing through the proxy, as direct access to the LogScale server in this configuration allows anyone to assume any identity.

Configure the proxy using the `AUTHENTICATION_METHOD` and `AUTH_BY_PROXY_HEADER_NAME` environment variables.

ini

    AUTHENTICATION_METHOD=byproxy
    AUTH_BY_PROXY_HEADER_NAME=name-of-http-header

The proxy must add a header with the username of the end user in the specified header. If the proxy leaves the header blank, the user does not get authenticated, and can only access shared dashboards.

LogScale uses the Authentication header as transport from the browser to the LogScale backend. Therefore, it is not possible to use a proxy that also uses this header. This rules out using `https://github.com/bitly/oauth2_proxy`.

#### Enter search term