Tls Mtls Spiffe
The proxy authorizes a client at the TLS handshake by the SPIFFE ID in its X.509-SVID client certificate
Versions marked “overview” do not contain this page. Selecting one opens that version’s documentation overview.
Category: Setup-dependent integration
Task: The proxy authorizes a client at the TLS handshake by the SPIFFE ID in its X.509-SVID client certificate
Prerequisites: The external service, credentials, or certificates referenced by this configuration.
This configuration comes from the selected release. The example has not been run here; external services are not bundled.
Download the source file.
# Listener mTLS with SPIFFE X.509-SVID Peer Identity (require_named)
#
# The proxy authorizes a client at the TLS handshake by the SPIFFE ID in its
# X.509-SVID client certificate. The certificate must chain to the trusted CA
# and its SPIFFE ID must be in trusted_spiffe_ids. An empty allowlist accepts any
# valid SVID the CA signs.
#
# Client (SVID) -> mTLS + SPIFFE -> Praxis :8443 -> HTTP -> Backend :3000
#
# ⚠️ EXPERIMENTAL: This example uses the `spiffe` experimental feature.
# Not recommended for production use. Build with --features spiffe.
#
# Usage:
# cargo run -p praxis-proxy --features spiffe -- -c examples/configs/protocols/tls-mtls-spiffe.yaml
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_named
trusted_spiffe_ids:
- spiffe://grid.internal/signals
filter_chains:
- name: main
filters:
- filter: router
routes:
- path_prefix: "/"
cluster: backend
- filter: load_balancer
clusters:
- name: backend
endpoints:
- "127.0.0.1:3000"
insecure_options:
allow_private_endpoints: true # example proxies to local backends