envoyproxy/envoy

domain specific TLS Configuration

Open

#44,021 opened on Mar 19, 2026

View on GitHub
 (10 comments) (0 reactions) (0 assignees)C++ (27,997 stars) (5,373 forks)batch import
area/tlsenhancementhelp wantedstale

Description

We use Envoy at Edge and we have need to configure domain specific TLS configuration such as Cipher Suites, TLS versions etc. As Envoy is used as Edge proxy and we can have huge number of domains so listing all domains and configure TLS properties using CommonTLSContext is not an option.

One option, I was thinking is to extend the on-demand cert selector and expand SDS for Per-Domain TLS Properties and when SDS delivers with certs + TLS properties, we can build new context also set cipher suites etc along with certs.

@kyessenov As discussed offline, created this issue. Can you please review and suggest any alternatives?

Contributor guide

Tech stack
cpp
Domain
infrastructuresecurity
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
C++EnvoyTLS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Study the on demand cert selector and SDS in Envoy. Propose a design for extending the cert selector to include TLS properties like cipher suites per domain. Look at the existing code for CommonTlsContext and the secret provider interface.