Configuration overview
This section provides configuration references for all DIAL components. It is intended for DevOps and platform engineers who deploy and operate DIAL.
These are reference pages — they document every option. For step-by-step authentication and access-control setup (API keys, JWT, and SSO / IdP), see Auth and access control.
Configuration files
DIAL uses JSON, XML, and YAML configuration files alongside environment variables. Each file has a dedicated reference page:
| File | Component | Format | Reload | Reference |
|---|---|---|---|---|
settings.json | DIAL Core | JSON | At startup (static) | Static settings |
config.json | DIAL Core | JSON | Every 60 seconds (dynamic) | How DIAL Core is configured |
gflog.xml | DIAL Core | XML | At startup | gflog.xml |
realm-config.json | Keycloak | JSON | At Keycloak startup | realm-config.json |
application.yaml | Auth Helper | YAML | At startup | Auth Helper |
docker-compose.yml | Docker Compose | YAML | At docker compose up | Docker Compose |
.env | Docker Compose | Key=Value | At docker compose up | .env reference |
values.yaml | DIAL Helm charts | YAML | At Helm install/upgrade | DIAL Helm configuration |
The reference for DIAL Core, DIAL Chat, DIAL Chat Themes, DIAL Model Provider, and the OpenAI, Bedrock, and Vertex AI adapters it runs is in Services.
Component reference pages
Components configured exclusively through environment variables:
| Component | What it covers | Page |
|---|---|---|
| DIAL Admin Frontend | Direct Core connection, administrator access, optional services, UI, and telemetry | Services > DIAL Admin |
| Admin Backend (optional) | Backend-managed configuration export/import, database, and authentication | Admin Backend configuration |
Documentation status
See Coverage status for a transparent list of what configuration documentation exists, what is partially covered, and what is planned.