Interface CommonTlsContextOrBuilder

  • All Superinterfaces:
    com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder
    All Known Implementing Classes:
    CommonTlsContext, CommonTlsContext.Builder

    public interface CommonTlsContextOrBuilder
    extends com.google.protobuf.MessageOrBuilder
    • Method Detail

      • hasTlsParams

        boolean hasTlsParams()
         TLS protocol versions, cipher suites etc.
         
        .envoy.extensions.transport_sockets.tls.v3.TlsParameters tls_params = 1;
      • getTlsParams

        TlsParameters getTlsParams()
         TLS protocol versions, cipher suites etc.
         
        .envoy.extensions.transport_sockets.tls.v3.TlsParameters tls_params = 1;
      • getTlsParamsOrBuilder

        TlsParametersOrBuilder getTlsParamsOrBuilder()
         TLS protocol versions, cipher suites etc.
         
        .envoy.extensions.transport_sockets.tls.v3.TlsParameters tls_params = 1;
      • getTlsCertificatesList

        List<TlsCertificate> getTlsCertificatesList()
         :ref:`Multiple TLS certificates <arch_overview_ssl_cert_select>` 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.
         Only one of *tls_certificates*, *tls_certificate_sds_secret_configs*,
         and *tls_certificate_provider_instance* may be used.
         [#next-major-version: These mutually exclusive fields should ideally be in a oneof, but it's
         not legal to put a repeated field in a oneof. In the next major version, we should rework
         this to avoid this problem.]
         
        repeated .envoy.extensions.transport_sockets.tls.v3.TlsCertificate tls_certificates = 2;
      • getTlsCertificates

        TlsCertificate getTlsCertificates​(int index)
         :ref:`Multiple TLS certificates <arch_overview_ssl_cert_select>` 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.
         Only one of *tls_certificates*, *tls_certificate_sds_secret_configs*,
         and *tls_certificate_provider_instance* may be used.
         [#next-major-version: These mutually exclusive fields should ideally be in a oneof, but it's
         not legal to put a repeated field in a oneof. In the next major version, we should rework
         this to avoid this problem.]
         
        repeated .envoy.extensions.transport_sockets.tls.v3.TlsCertificate tls_certificates = 2;
      • getTlsCertificatesCount

        int getTlsCertificatesCount()
         :ref:`Multiple TLS certificates <arch_overview_ssl_cert_select>` 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.
         Only one of *tls_certificates*, *tls_certificate_sds_secret_configs*,
         and *tls_certificate_provider_instance* may be used.
         [#next-major-version: These mutually exclusive fields should ideally be in a oneof, but it's
         not legal to put a repeated field in a oneof. In the next major version, we should rework
         this to avoid this problem.]
         
        repeated .envoy.extensions.transport_sockets.tls.v3.TlsCertificate tls_certificates = 2;
      • getTlsCertificatesOrBuilderList

        List<? extends TlsCertificateOrBuilder> getTlsCertificatesOrBuilderList()
         :ref:`Multiple TLS certificates <arch_overview_ssl_cert_select>` 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.
         Only one of *tls_certificates*, *tls_certificate_sds_secret_configs*,
         and *tls_certificate_provider_instance* may be used.
         [#next-major-version: These mutually exclusive fields should ideally be in a oneof, but it's
         not legal to put a repeated field in a oneof. In the next major version, we should rework
         this to avoid this problem.]
         
        repeated .envoy.extensions.transport_sockets.tls.v3.TlsCertificate tls_certificates = 2;
      • getTlsCertificatesOrBuilder

        TlsCertificateOrBuilder getTlsCertificatesOrBuilder​(int index)
         :ref:`Multiple TLS certificates <arch_overview_ssl_cert_select>` 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.
         Only one of *tls_certificates*, *tls_certificate_sds_secret_configs*,
         and *tls_certificate_provider_instance* may be used.
         [#next-major-version: These mutually exclusive fields should ideally be in a oneof, but it's
         not legal to put a repeated field in a oneof. In the next major version, we should rework
         this to avoid this problem.]
         
        repeated .envoy.extensions.transport_sockets.tls.v3.TlsCertificate tls_certificates = 2;
      • getTlsCertificateSdsSecretConfigsList

        List<SdsSecretConfig> getTlsCertificateSdsSecretConfigsList()
         Configs for fetching TLS certificates via SDS API. Note SDS API allows certificates to be
         fetched/refreshed over the network asynchronously with respect to the TLS handshake.
         The same number and types of certificates as :ref:`tls_certificates <envoy_v3_api_field_extensions.transport_sockets.tls.v3.CommonTlsContext.tls_certificates>`
         are valid in the the certificates fetched through this setting.
         Only one of *tls_certificates*, *tls_certificate_sds_secret_configs*,
         and *tls_certificate_provider_instance* may be used.
         [#next-major-version: These mutually exclusive fields should ideally be in a oneof, but it's
         not legal to put a repeated field in a oneof. In the next major version, we should rework
         this to avoid this problem.]
         
        repeated .envoy.extensions.transport_sockets.tls.v3.SdsSecretConfig tls_certificate_sds_secret_configs = 6 [(.validate.rules) = { ... }
      • getTlsCertificateSdsSecretConfigs

        SdsSecretConfig getTlsCertificateSdsSecretConfigs​(int index)
         Configs for fetching TLS certificates via SDS API. Note SDS API allows certificates to be
         fetched/refreshed over the network asynchronously with respect to the TLS handshake.
         The same number and types of certificates as :ref:`tls_certificates <envoy_v3_api_field_extensions.transport_sockets.tls.v3.CommonTlsContext.tls_certificates>`
         are valid in the the certificates fetched through this setting.
         Only one of *tls_certificates*, *tls_certificate_sds_secret_configs*,
         and *tls_certificate_provider_instance* may be used.
         [#next-major-version: These mutually exclusive fields should ideally be in a oneof, but it's
         not legal to put a repeated field in a oneof. In the next major version, we should rework
         this to avoid this problem.]
         
        repeated .envoy.extensions.transport_sockets.tls.v3.SdsSecretConfig tls_certificate_sds_secret_configs = 6 [(.validate.rules) = { ... }
      • getTlsCertificateSdsSecretConfigsCount

        int getTlsCertificateSdsSecretConfigsCount()
         Configs for fetching TLS certificates via SDS API. Note SDS API allows certificates to be
         fetched/refreshed over the network asynchronously with respect to the TLS handshake.
         The same number and types of certificates as :ref:`tls_certificates <envoy_v3_api_field_extensions.transport_sockets.tls.v3.CommonTlsContext.tls_certificates>`
         are valid in the the certificates fetched through this setting.
         Only one of *tls_certificates*, *tls_certificate_sds_secret_configs*,
         and *tls_certificate_provider_instance* may be used.
         [#next-major-version: These mutually exclusive fields should ideally be in a oneof, but it's
         not legal to put a repeated field in a oneof. In the next major version, we should rework
         this to avoid this problem.]
         
        repeated .envoy.extensions.transport_sockets.tls.v3.SdsSecretConfig tls_certificate_sds_secret_configs = 6 [(.validate.rules) = { ... }
      • getTlsCertificateSdsSecretConfigsOrBuilderList

        List<? extends SdsSecretConfigOrBuilder> getTlsCertificateSdsSecretConfigsOrBuilderList()
         Configs for fetching TLS certificates via SDS API. Note SDS API allows certificates to be
         fetched/refreshed over the network asynchronously with respect to the TLS handshake.
         The same number and types of certificates as :ref:`tls_certificates <envoy_v3_api_field_extensions.transport_sockets.tls.v3.CommonTlsContext.tls_certificates>`
         are valid in the the certificates fetched through this setting.
         Only one of *tls_certificates*, *tls_certificate_sds_secret_configs*,
         and *tls_certificate_provider_instance* may be used.
         [#next-major-version: These mutually exclusive fields should ideally be in a oneof, but it's
         not legal to put a repeated field in a oneof. In the next major version, we should rework
         this to avoid this problem.]
         
        repeated .envoy.extensions.transport_sockets.tls.v3.SdsSecretConfig tls_certificate_sds_secret_configs = 6 [(.validate.rules) = { ... }
      • getTlsCertificateSdsSecretConfigsOrBuilder

        SdsSecretConfigOrBuilder getTlsCertificateSdsSecretConfigsOrBuilder​(int index)
         Configs for fetching TLS certificates via SDS API. Note SDS API allows certificates to be
         fetched/refreshed over the network asynchronously with respect to the TLS handshake.
         The same number and types of certificates as :ref:`tls_certificates <envoy_v3_api_field_extensions.transport_sockets.tls.v3.CommonTlsContext.tls_certificates>`
         are valid in the the certificates fetched through this setting.
         Only one of *tls_certificates*, *tls_certificate_sds_secret_configs*,
         and *tls_certificate_provider_instance* may be used.
         [#next-major-version: These mutually exclusive fields should ideally be in a oneof, but it's
         not legal to put a repeated field in a oneof. In the next major version, we should rework
         this to avoid this problem.]
         
        repeated .envoy.extensions.transport_sockets.tls.v3.SdsSecretConfig tls_certificate_sds_secret_configs = 6 [(.validate.rules) = { ... }
      • hasTlsCertificateProviderInstance

        boolean hasTlsCertificateProviderInstance()
         Certificate provider instance for fetching TLS certs.
         Only one of *tls_certificates*, *tls_certificate_sds_secret_configs*,
         and *tls_certificate_provider_instance* may be used.
         [#not-implemented-hide:]
         
        .envoy.extensions.transport_sockets.tls.v3.CertificateProviderPluginInstance tls_certificate_provider_instance = 14;
      • getTlsCertificateProviderInstance

        CertificateProviderPluginInstance getTlsCertificateProviderInstance()
         Certificate provider instance for fetching TLS certs.
         Only one of *tls_certificates*, *tls_certificate_sds_secret_configs*,
         and *tls_certificate_provider_instance* may be used.
         [#not-implemented-hide:]
         
        .envoy.extensions.transport_sockets.tls.v3.CertificateProviderPluginInstance tls_certificate_provider_instance = 14;
      • getTlsCertificateProviderInstanceOrBuilder

        CertificateProviderPluginInstanceOrBuilder getTlsCertificateProviderInstanceOrBuilder()
         Certificate provider instance for fetching TLS certs.
         Only one of *tls_certificates*, *tls_certificate_sds_secret_configs*,
         and *tls_certificate_provider_instance* may be used.
         [#not-implemented-hide:]
         
        .envoy.extensions.transport_sockets.tls.v3.CertificateProviderPluginInstance tls_certificate_provider_instance = 14;
      • hasTlsCertificateCertificateProvider

        @Deprecated
        boolean hasTlsCertificateCertificateProvider()
        Deprecated.
         Certificate provider for fetching TLS certificates.
         [#not-implemented-hide:]
         
        .envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.CertificateProvider tls_certificate_certificate_provider = 9 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      • getTlsCertificateCertificateProvider

        @Deprecated
        CommonTlsContext.CertificateProvider getTlsCertificateCertificateProvider()
        Deprecated.
         Certificate provider for fetching TLS certificates.
         [#not-implemented-hide:]
         
        .envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.CertificateProvider tls_certificate_certificate_provider = 9 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      • getTlsCertificateCertificateProviderOrBuilder

        @Deprecated
        CommonTlsContext.CertificateProviderOrBuilder getTlsCertificateCertificateProviderOrBuilder()
        Deprecated.
         Certificate provider for fetching TLS certificates.
         [#not-implemented-hide:]
         
        .envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.CertificateProvider tls_certificate_certificate_provider = 9 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      • hasTlsCertificateCertificateProviderInstance

        @Deprecated
        boolean hasTlsCertificateCertificateProviderInstance()
        Deprecated.
         Certificate provider instance for fetching TLS certificates.
         [#not-implemented-hide:]
         
        .envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.CertificateProviderInstance tls_certificate_certificate_provider_instance = 11 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      • getTlsCertificateCertificateProviderInstance

        @Deprecated
        CommonTlsContext.CertificateProviderInstance getTlsCertificateCertificateProviderInstance()
        Deprecated.
         Certificate provider instance for fetching TLS certificates.
         [#not-implemented-hide:]
         
        .envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.CertificateProviderInstance tls_certificate_certificate_provider_instance = 11 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      • getTlsCertificateCertificateProviderInstanceOrBuilder

        @Deprecated
        CommonTlsContext.CertificateProviderInstanceOrBuilder getTlsCertificateCertificateProviderInstanceOrBuilder()
        Deprecated.
         Certificate provider instance for fetching TLS certificates.
         [#not-implemented-hide:]
         
        .envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.CertificateProviderInstance tls_certificate_certificate_provider_instance = 11 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      • hasValidationContext

        boolean hasValidationContext()
         How to validate peer certificates.
         
        .envoy.extensions.transport_sockets.tls.v3.CertificateValidationContext validation_context = 3;
      • getValidationContext

        CertificateValidationContext getValidationContext()
         How to validate peer certificates.
         
        .envoy.extensions.transport_sockets.tls.v3.CertificateValidationContext validation_context = 3;
      • getValidationContextOrBuilder

        CertificateValidationContextOrBuilder getValidationContextOrBuilder()
         How to validate peer certificates.
         
        .envoy.extensions.transport_sockets.tls.v3.CertificateValidationContext validation_context = 3;
      • hasValidationContextSdsSecretConfig

        boolean hasValidationContextSdsSecretConfig()
         Config for fetching validation context via SDS API. Note SDS API allows certificates to be
         fetched/refreshed over the network asynchronously with respect to the TLS handshake.
         
        .envoy.extensions.transport_sockets.tls.v3.SdsSecretConfig validation_context_sds_secret_config = 7;
      • getValidationContextSdsSecretConfig

        SdsSecretConfig getValidationContextSdsSecretConfig()
         Config for fetching validation context via SDS API. Note SDS API allows certificates to be
         fetched/refreshed over the network asynchronously with respect to the TLS handshake.
         
        .envoy.extensions.transport_sockets.tls.v3.SdsSecretConfig validation_context_sds_secret_config = 7;
      • getValidationContextSdsSecretConfigOrBuilder

        SdsSecretConfigOrBuilder getValidationContextSdsSecretConfigOrBuilder()
         Config for fetching validation context via SDS API. Note SDS API allows certificates to be
         fetched/refreshed over the network asynchronously with respect to the TLS handshake.
         
        .envoy.extensions.transport_sockets.tls.v3.SdsSecretConfig validation_context_sds_secret_config = 7;
      • hasCombinedValidationContext

        boolean hasCombinedValidationContext()
         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.
         
        .envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.CombinedCertificateValidationContext combined_validation_context = 8;
      • getCombinedValidationContext

        CommonTlsContext.CombinedCertificateValidationContext getCombinedValidationContext()
         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.
         
        .envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.CombinedCertificateValidationContext combined_validation_context = 8;
      • getCombinedValidationContextOrBuilder

        CommonTlsContext.CombinedCertificateValidationContextOrBuilder getCombinedValidationContextOrBuilder()
         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.
         
        .envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.CombinedCertificateValidationContext combined_validation_context = 8;
      • hasValidationContextCertificateProvider

        @Deprecated
        boolean hasValidationContextCertificateProvider()
        Deprecated.
         Certificate provider for fetching validation context.
         [#not-implemented-hide:]
         
        .envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.CertificateProvider validation_context_certificate_provider = 10 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      • getValidationContextCertificateProvider

        @Deprecated
        CommonTlsContext.CertificateProvider getValidationContextCertificateProvider()
        Deprecated.
         Certificate provider for fetching validation context.
         [#not-implemented-hide:]
         
        .envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.CertificateProvider validation_context_certificate_provider = 10 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      • getValidationContextCertificateProviderOrBuilder

        @Deprecated
        CommonTlsContext.CertificateProviderOrBuilder getValidationContextCertificateProviderOrBuilder()
        Deprecated.
         Certificate provider for fetching validation context.
         [#not-implemented-hide:]
         
        .envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.CertificateProvider validation_context_certificate_provider = 10 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      • hasValidationContextCertificateProviderInstance

        @Deprecated
        boolean hasValidationContextCertificateProviderInstance()
        Deprecated.
         Certificate provider instance for fetching validation context.
         [#not-implemented-hide:]
         
        .envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.CertificateProviderInstance validation_context_certificate_provider_instance = 12 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      • getValidationContextCertificateProviderInstance

        @Deprecated
        CommonTlsContext.CertificateProviderInstance getValidationContextCertificateProviderInstance()
        Deprecated.
         Certificate provider instance for fetching validation context.
         [#not-implemented-hide:]
         
        .envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.CertificateProviderInstance validation_context_certificate_provider_instance = 12 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      • getValidationContextCertificateProviderInstanceOrBuilder

        @Deprecated
        CommonTlsContext.CertificateProviderInstanceOrBuilder getValidationContextCertificateProviderInstanceOrBuilder()
        Deprecated.
         Certificate provider instance for fetching validation context.
         [#not-implemented-hide:]
         
        .envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.CertificateProviderInstance validation_context_certificate_provider_instance = 12 [deprecated = true, (.envoy.annotations.deprecated_at_minor_version) = "3.0"];
      • getAlpnProtocolsList

        List<String> getAlpnProtocolsList()
         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
         :ref:`codec_type
         <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.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.
         
        repeated string alpn_protocols = 4;
      • getAlpnProtocolsCount

        int getAlpnProtocolsCount()
         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
         :ref:`codec_type
         <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.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.
         
        repeated string alpn_protocols = 4;
      • getAlpnProtocols

        String getAlpnProtocols​(int index)
         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
         :ref:`codec_type
         <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.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.
         
        repeated string alpn_protocols = 4;
      • getAlpnProtocolsBytes

        com.google.protobuf.ByteString getAlpnProtocolsBytes​(int index)
         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
         :ref:`codec_type
         <envoy_v3_api_field_extensions.filters.network.http_connection_manager.v3.HttpConnectionManager.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.
         
        repeated string alpn_protocols = 4;
      • hasCustomHandshaker

        boolean hasCustomHandshaker()
         Custom TLS handshaker. If empty, defaults to native TLS handshaking
         behavior.
         
        .envoy.config.core.v3.TypedExtensionConfig custom_handshaker = 13;
      • getCustomHandshaker

        TypedExtensionConfig getCustomHandshaker()
         Custom TLS handshaker. If empty, defaults to native TLS handshaking
         behavior.
         
        .envoy.config.core.v3.TypedExtensionConfig custom_handshaker = 13;
      • getCustomHandshakerOrBuilder

        TypedExtensionConfigOrBuilder getCustomHandshakerOrBuilder()
         Custom TLS handshaker. If empty, defaults to native TLS handshaking
         behavior.
         
        .envoy.config.core.v3.TypedExtensionConfig custom_handshaker = 13;
      • hasKeyLog

        boolean hasKeyLog()
         TLS key log configuration
         
        .envoy.extensions.transport_sockets.tls.v3.TlsKeyLog key_log = 15;
      • getKeyLog

        TlsKeyLog getKeyLog()
         TLS key log configuration
         
        .envoy.extensions.transport_sockets.tls.v3.TlsKeyLog key_log = 15;
      • getKeyLogOrBuilder

        TlsKeyLogOrBuilder getKeyLogOrBuilder()
         TLS key log configuration
         
        .envoy.extensions.transport_sockets.tls.v3.TlsKeyLog key_log = 15;