Configuration

Configuration reference for ProxyConf

ProxyConf is configured through two mechanisms:

  1. Environment Variables - Configure the ProxyConf server itself (ports, database, TLS, etc.)
  2. OpenAPI Extensions - Configure how each API is exposed through Envoy using x-proxyconf

Configuration Overview

┌─────────────────────────────────────────────────────────────────┐
│                    ProxyConf Configuration                      │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  Environment Variables          OpenAPI x-proxyconf Extension   │
│  ─────────────────────          ───────────────────────────────│
│  • Server ports                 • API routing (url, listener)   │
│  • Database connection          • Authentication (downstream)   │
│  • TLS certificates             • Credential injection (up.)    │
│  • Cluster defaults             • CORS policies                 │
│  • Logging                      • Request validation            │
│                                 • HTTP connection settings      │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

In This Section

PageDescription
Environment VariablesConfigure ProxyConf server settings via environment variables
OpenAPI ExtensionReference for the x-proxyconf OpenAPI extension
Downstream AuthenticationConfigure client authentication (API keys, JWT, mTLS, Basic)
Upstream AuthenticationInject credentials when calling upstream services
CORSConfigure Cross-Origin Resource Sharing policies
HTTP Connection ManagerFine-tune Envoy’s HTTP connection handling

Quick Reference

Minimal OpenAPI Configuration

openapi: 3.0.3
info:
  title: My API
  version: 1.0.0
x-proxyconf:
  cluster: my-cluster
  url: https://api.example.com/my-api
  security:
    auth:
      downstream:
        disabled: {}
paths:
  /health:
    get:
      summary: Health check
      responses:
        '200':
          description: OK

Common Configuration Patterns

Use CaseKey Configuration
Public API (no auth)security.auth.downstream.disabled: {}
API Key authenticationsecurity.auth.downstream.type: header
JWT authenticationsecurity.auth.downstream.jwt: {...}
mTLS authenticationsecurity.auth.downstream.mtls: {...}
IP allowlistingsecurity.allowed-source-ips: [...]
Custom upstream authsecurity.auth.upstream: {...}