Common TLS configuration

auth.TlsParameters

[auth.TlsParameters proto]

  1. {
  2.   "tls_minimum_protocol_version": "...",
  3.   "tls_maximum_protocol_version": "...",
  4.   "cipher_suites": [],
  5.   "ecdh_curves": []
  6. }

tls_minimum_protocol_version

(auth.TlsParameters.TlsProtocol) Minimum TLS protocol version. By default, it’s TLSv1_0.

tls_maximum_protocol_version

(auth.TlsParameters.TlsProtocol) Maximum TLS protocol version. By default, it’s TLSv1_3 for servers in non-FIPS builds, and TLSv1_2 for clients and for servers using BoringSSL FIPS.

cipher_suites

(string) If specified, the TLS listener will only support the specified cipher list when negotiating TLS 1.0-1.2 (this setting has no effect when negotiating TLS 1.3). If not specified, the default list will be used.

In non-FIPS builds, the default cipher list is:

  1. [ECDHE-ECDSA-AES128-GCM-SHA256|ECDHE-ECDSA-CHACHA20-POLY1305]
  2. [ECDHE-RSA-AES128-GCM-SHA256|ECDHE-RSA-CHACHA20-POLY1305]
  3. ECDHE-ECDSA-AES128-SHA
  4. ECDHE-RSA-AES128-SHA
  5. AES128-GCM-SHA256
  6. AES128-SHA
  7. ECDHE-ECDSA-AES256-GCM-SHA384
  8. ECDHE-RSA-AES256-GCM-SHA384
  9. ECDHE-ECDSA-AES256-SHA
  10. ECDHE-RSA-AES256-SHA
  11. AES256-GCM-SHA384
  12. AES256-SHA

In builds using BoringSSL FIPS, the default cipher list is:

  1. ECDHE-ECDSA-AES128-GCM-SHA256
  2. ECDHE-RSA-AES128-GCM-SHA256
  3. ECDHE-ECDSA-AES128-SHA
  4. ECDHE-RSA-AES128-SHA
  5. AES128-GCM-SHA256
  6. AES128-SHA
  7. ECDHE-ECDSA-AES256-GCM-SHA384
  8. ECDHE-RSA-AES256-GCM-SHA384
  9. ECDHE-ECDSA-AES256-SHA
  10. ECDHE-RSA-AES256-SHA
  11. AES256-GCM-SHA384
  12. AES256-SHA

ecdh_curves

(string) If specified, the TLS connection will only support the specified ECDH curves. If not specified, the default curves will be used.

In non-FIPS builds, the default curves are:

  1. X25519
  2. P-256

In builds using BoringSSL FIPS, the default curve is:

  1. P-256

Enum auth.TlsParameters.TlsProtocol

[auth.TlsParameters.TlsProtocol proto]

TLS_AUTO

(DEFAULT) ⁣Envoy will choose the optimal TLS version.

TLSv1_0

⁣TLS 1.0

TLSv1_1

⁣TLS 1.1

TLSv1_2

⁣TLS 1.2

TLSv1_3

⁣TLS 1.3

auth.TlsCertificate

[auth.TlsCertificate proto]

  1. {
  2.   "certificate_chain": "{...}",
  3.   "private_key": "{...}",
  4.   "password": "{...}"
  5. }

certificate_chain

(core.DataSource) The TLS certificate chain.

private_key

(core.DataSource) The TLS private key.

password

(core.DataSource) The password to decrypt the TLS private key. If this field is not set, it is assumed that the TLS private key is not password encrypted.

auth.TlsSessionTicketKeys

[auth.TlsSessionTicketKeys proto]

  1. {
  2.   "keys": []
  3. }

keys

(core.DataSource, REQUIRED) Keys for encrypting and decrypting TLS session tickets. The first key in the array contains the key to encrypt all new sessions created by this context. All keys are candidates for decrypting received tickets. This allows for easy rotation of keys by, for example, putting the new key first, and the previous key second.

If session_ticket_keys is not specified, the TLS library will still support resuming sessions via tickets, but it will use an internally-generated and managed key, so sessions cannot be resumed across hot restarts or on different hosts.

Each key must contain exactly 80 bytes of cryptographically-secure random data. For example, the output of openssl rand 80.

Attention

Using this feature has serious security considerations and risks. Improper handling of keys may result in loss of secrecy in connections, even if ciphers supporting perfect forward secrecy are used. See https://www.imperialviolet.org/2013/06/27/botchingpfs.html for some discussion. To minimize the risk, you must:

  • Keep the session ticket keys at least as secure as your TLS certificate private keys
  • Rotate session ticket keys at least daily, and preferably hourly
  • Always generate keys using a cryptographically-secure random data source

auth.CertificateValidationContext

[auth.CertificateValidationContext proto]

  1. {
  2.   "trusted_ca": "{...}",
  3.   "verify_certificate_spki": [],
  4.   "verify_certificate_hash": [],
  5.   "verify_subject_alt_name": [],
  6.   "crl": "{...}",
  7.   "allow_expired_certificate": "..."
  8. }

trusted_ca

(core.DataSource) TLS certificate data containing certificate authority certificates to use in verifying a presented peer certificate (e.g. server certificate for clusters or client certificate for listeners). If not specified and a peer certificate is presented it will not be verified. By default, a client certificate is optional, unless one of the additional options (require_client_certificate, verify_certificate_spki, verify_certificate_hash, or verify_subject_alt_name) is also specified.

It can optionally contain certificate revocation lists, in which case Envoy will verify that the presented peer certificate has not been revoked by one of the included CRLs.

See the TLS overview for a list of common system CA locations.

verify_certificate_spki

(string) An optional list of base64-encoded SHA-256 hashes. If specified, Envoy will verify that the SHA-256 of the DER-encoded Subject Public Key Information (SPKI) of the presented certificate matches one of the specified values.

A base64-encoded SHA-256 of the Subject Public Key Information (SPKI) of the certificate can be generated with the following command:

  1. $ openssl x509 -in path/to/client.crt -noout -pubkey \
  2.   | openssl pkey -pubin -outform DER \
  3.   | openssl dgst -sha256 -binary \
  4.   | openssl enc -base64
  5. NvqYIYSbgK2vCJpQhObf77vv+bQWtc5ek5RIOwPiC9A=

This is the format used in HTTP Public Key Pinning.

When both: verify_certificate_hash and verify_certificate_spki are specified, a hash matching value from either of the lists will result in the certificate being accepted.

Attention

This option is preferred over verify_certificate_hash, because SPKI is tied to a private key, so it doesn’t change when the certificate is renewed using the same private key.

verify_certificate_hash

(string) An optional list of hex-encoded SHA-256 hashes. If specified, Envoy will verify that the SHA-256 of the DER-encoded presented certificate matches one of the specified values.

A hex-encoded SHA-256 of the certificate can be generated with the following command:

  1. $ openssl x509 -in path/to/client.crt -outform DER | openssl dgst -sha256 | cut -d" " -f2
  2. df6ff72fe9116521268f6f2dd4966f51df479883fe7037b39f75916ac3049d1a

A long hex-encoded and colon-separated SHA-256 (a.k.a. “fingerprint”) of the certificate can be generated with the following command:

  1. $ openssl x509 -in path/to/client.crt -noout -fingerprint -sha256 | cut -d"=" -f2
  2. DF:6F:F7:2F:E9:11:65:21:26:8F:6F:2D:D4:96:6F:51:DF:47:98:83:FE:70:37:B3:9F:75:91:6A:C3:04:9D:1A

Both of those formats are acceptable.

When both: verify_certificate_hash and verify_certificate_spki are specified, a hash matching value from either of the lists will result in the certificate being accepted.

verify_subject_alt_name

(string) An optional list of Subject Alternative Names. If specified, Envoy will verify that the Subject Alternative Name of the presented certificate matches one of the specified values.

Attention

Subject Alternative Names are easily spoofable and verifying only them is insecure, therefore this option must be used together with trusted_ca.

crl

(core.DataSource) An optional certificate revocation list (in PEM format). If specified, Envoy will verify that the presented peer certificate has not been revoked by this CRL. If this DataSource contains multiple CRLs, all of them will be used.

allow_expired_certificate

(bool) If specified, Envoy will not reject expired certificates.

auth.CommonTlsContext

[auth.CommonTlsContext proto]

TLS context shared by both client and server TLS contexts.

  1. {
  2.   "tls_params": "{...}",
  3.   "tls_certificates": [],
  4.   "tls_certificate_sds_secret_configs": [],
  5.   "validation_context": "{...}",
  6.   "validation_context_sds_secret_config": "{...}",
  7.   "combined_validation_context": "{...}",
  8.   "alpn_protocols": []
  9. }

tls_params

(auth.TlsParameters) TLS protocol versions, cipher suites etc.

tls_certificates

(auth.TlsCertificate) Multiple TLS certificates can be associated with the same context to allow both RSA and ECDSA certificates.

Only a single TLS certificate is supported in client contexts. In server contexts, the first RSA certificate is used for clients that only support RSA and the first ECDSA certificate is used for clients that support ECDSA.

tls_certificate_sds_secret_configs

(auth.SdsSecretConfig) Configs for fetching TLS certificates via SDS API.

validation_context

(auth.CertificateValidationContext) How to validate peer certificates.

Only one of validation_context, validation_context_sds_secret_config, combined_validation_context may be set.

validation_context_sds_secret_config

(auth.SdsSecretConfig) Config for fetching validation context via SDS API.

Only one of validation_context, validation_context_sds_secret_config, combined_validation_context may be set.

combined_validation_context

(auth.CommonTlsContext.CombinedCertificateValidationContext) Combined certificate validation context holds a default CertificateValidationContext and SDS config. When SDS server returns dynamic CertificateValidationContext, both dynamic and default CertificateValidationContext are merged into a new CertificateValidationContext for validation. This merge is done by Message::MergeFrom(), so dynamic CertificateValidationContext overwrites singular fields in default CertificateValidationContext, and concatenates repeated fields to default CertificateValidationContext, and logical OR is applied to boolean fields.

Only one of validation_context, validation_context_sds_secret_config, combined_validation_context may be set.

alpn_protocols

(string) Supplies the list of ALPN protocols that the listener should expose. In practice this is likely to be set to one of two values (see the codec_type parameter in the HTTP connection manager for more information):

  • “h2,http/1.1” If the listener is going to support both HTTP/2 and HTTP/1.1.
  • “http/1.1” If the listener is only going to support HTTP/1.1.

There is no default for this parameter. If empty, Envoy will not expose ALPN.

auth.CommonTlsContext.CombinedCertificateValidationContext

[auth.CommonTlsContext.CombinedCertificateValidationContext proto]

  1. {
  2.   "default_validation_context": "{...}",
  3.   "validation_context_sds_secret_config": "{...}"
  4. }

default_validation_context

(auth.CertificateValidationContext, REQUIRED) How to validate peer certificates.

validation_context_sds_secret_config

(auth.SdsSecretConfig, REQUIRED) Config for fetching validation context via SDS API.

auth.UpstreamTlsContext

[auth.UpstreamTlsContext proto]

  1. {
  2.   "common_tls_context": "{...}",
  3.   "sni": "...",
  4.   "allow_renegotiation": "...",
  5.   "max_session_keys": "{...}"
  6. }

common_tls_context

(auth.CommonTlsContext) Common TLS context settings.

sni

(string) SNI string to use when creating TLS backend connections.

allow_renegotiation

(bool) If true, server-initiated TLS renegotiation will be allowed.

Attention

TLS renegotiation is considered insecure and shouldn’t be used unless absolutely necessary.

max_session_keys

(UInt32Value) Maximum number of session keys (Pre-Shared Keys for TLSv1.3+, Session IDs and Session Tickets for TLSv1.2 and older) to store for the purpose of session resumption.

Defaults to 1, setting this to 0 disables session resumption.

auth.DownstreamTlsContext

[auth.DownstreamTlsContext proto]

  1. {
  2.   "common_tls_context": "{...}",
  3.   "require_client_certificate": "{...}",
  4.   "session_ticket_keys": "{...}"
  5. }

common_tls_context

(auth.CommonTlsContext) Common TLS context settings.

require_client_certificate

(BoolValue) If specified, Envoy will reject connections without a valid client certificate.

session_ticket_keys

(auth.TlsSessionTicketKeys) TLS session ticket key settings.

auth.SdsSecretConfig

[auth.SdsSecretConfig proto]

Warning

This message type has experimental status.

  1. {
  2.   "name": "...",
  3.   "sds_config": "{...}"
  4. }

name

(string) Name (FQDN, UUID, SPKI, SHA256, etc.) by which the secret can be uniquely referred to. When both name and config are specified, then secret can be fetched and/or reloaded via SDS. When only name is specified, then secret will be loaded from static resources [V2-API-DIFF].

sds_config

(core.ConfigSource)

auth.Secret

[auth.Secret proto]

Warning

This message type has experimental status.

  1. {
  2.   "name": "...",
  3.   "tls_certificate": "{...}",
  4.   "session_ticket_keys": "{...}",
  5.   "validation_context": "{...}"
  6. }

name

(string) Name (FQDN, UUID, SPKI, SHA256, etc.) by which the secret can be uniquely referred to.

tls_certificate

(auth.TlsCertificate)

Only one of tls_certificate, session_ticket_keys, validation_context may be set.

session_ticket_keys

(auth.TlsSessionTicketKeys)

Only one of tls_certificate, session_ticket_keys, validation_context may be set.

validation_context

(auth.CertificateValidationContext)

Only one of tls_certificate, session_ticket_keys, validation_context may be set.