Kibana - Auth Proxy Setup & Configuration

Overview

The Kibana Auth Proxy is like a security gateway for Kibana.

• It is a layer between users and Kibana to make sure only authorised people can get in.

• It checks each request using DIGIT’s login system before allowing access.

You can easily customise how it works by setting environment variables (for example, which port it uses, which login service it talks to, and which websites are allowed).

It’s ready to install using Helm charts, which makes deployment fast. Technically, it’s built using Node.js and works as a “reverse proxy” — meaning all traffic goes through it before reaching Kibana.

Setup & Configuration

The service relies on environment variables defined in envVariables for key configuration. These variables include:

The variables enable users to customise the proxy’s behaviour and handlers:

Variable	Purpose
SERVER_PORT	Port on which the proxy runs
EGOV_USER_HOST / _SEARCH	Defines the host and endpoint for the external auth API
KIBANA_HOST / _BASE_PATH	URL and base path of the Kibana server
KIBANA_ACCEPTED_CONTEXT_UI_PATHS	Valid referer paths for access control
KIBANA_ACCEPTED_DOMAIN_NAME	Domain(s) allowed to access Kibana
KIBANA_EXCLUDE_URL_PATTERNS	URL patterns that bypass authentication

These settings can be overridden with environment variables during deployment.

Deployment Configuration

The deployment details given in the Helm Charts repo here ensure the auth-proxy is easily deployed into your infrastructure.

Build Details

Auth-Proxy: auth-proxy-urlencoded-fix-aad9a5959c-23