> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/v1.5/hcm-product-suite/health-products/campaign-management-dashboard/kibana-dashboard-integration-with-dss-module/auth-proxy-setup-and-configuration-for-kibana.md).

# Auth Proxy Setup and Configuration for Kibana

## Overview

This Node.js service acts as a reverse proxy for Kibana, enforcing authentication and access control based on specific rules. It validates requests using DIGIT’s authentication API.The service utilizes express, express-http-proxy, and axios for proxying and API interaction.<br>

## Setup & Configuration

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

These configurations can be overridden by environment variables, and they include:

* SERVER\_PORT: The port on which the Node.js service will run.
* EGOV\_USER\_HOST and EGOV\_USER\_SEARCH: The host and path for the external authentication API.
* KIBANA\_HOST and KIBANA\_BASE\_PATH: The Kibana server URL and base path.
* KIBANA\_ACCEPTED\_CONTEXT\_UI\_PATHS: List of valid context paths for referer validation.
* KIBANA\_ACCEPTED\_DOMAIN\_NAME: Domain name allowed for Kibana access.
* KIBANA\_EXCLUDE\_URL\_PATTERNS: URL patterns excluded from authentication.

## Deployment Configuration

[Helm Charts](https://github.com/egovernments/DIGIT-DevOps/tree/unified-env/deploy-as-code/helm/charts/health-services/auth-proxy)

## Build Details

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


---

# 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 by asking a question.

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

```
GET https://docs.digit.org/health/v1.5/hcm-product-suite/health-products/campaign-management-dashboard/kibana-dashboard-integration-with-dss-module/auth-proxy-setup-and-configuration-for-kibana.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 `automate deployments from our CI pipeline` 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.