Tls Mtls Both

Client mTLS to the proxy (client cert required), and proxy mTLS to the upstream backend (proxy presents its own client certificate)

Category: Setup-dependent integration
Task: Client mTLS to the proxy (client cert required), and proxy mTLS to the upstream backend (proxy presents its own client certificate)

Prerequisites: The external service, credentials, or certificates referenced by this configuration.

Run it: Use ghcr.io/praxis-proxy/praxis:0.7.2 and follow the first reverse-proxy tutorial to mount and start the configuration.

This configuration comes from the selected release. The example has not been run here; external services are not bundled.

Download the source file.

# Full mTLS (Both Directions)
#
# Client mTLS to the proxy (client cert required), and
# proxy mTLS to the upstream backend (proxy presents its
# own client certificate).
#
#   Client -> mTLS -> Praxis :8443 -> mTLS -> Backend :9443
#
insecure_options:
  allow_private_endpoints: true # example proxies to local backends
  allow_tls_no_verify: true

listeners:
  - name: secure
    address: "127.0.0.1:8443"
    filter_chains:
      - main
    tls:
      certificates:
        - cert_path: /etc/ssl/certs/server.pem
          key_path: /etc/ssl/private/server-key.pem
      client_ca:
        ca_path: /etc/ssl/certs/client-ca.pem
      client_cert_mode: require

filter_chains:
  - name: main
    filters:
      - filter: router
        routes:
          - path_prefix: "/"
            cluster: backend

      - filter: load_balancer
        clusters:
          - name: backend
            tls:
              verify: false # dev only
              client_cert:
                cert_path: /etc/ssl/certs/proxy-client.pem
                key_path: /etc/ssl/private/proxy-client-key.pem
            endpoints:
              - "127.0.0.1:9443"