Package io.envoyproxy.envoy.extensions.transport_sockets.tls.v3

Class CommonTlsContext.Builder

  • All Implemented Interfaces:
    com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, CommonTlsContextOrBuilder, Cloneable
    Enclosing class:
    CommonTlsContext
    public static final class CommonTlsContext.Builder
extends com.google.protobuf.GeneratedMessageV3.Builder<CommonTlsContext.Builder>
implements CommonTlsContextOrBuilder
     TLS context shared by both client and server TLS contexts.
 [#next-free-field: 16]
    Protobuf type envoy.extensions.transport_sockets.tls.v3.CommonTlsContext

    • Method Detail

      • getDescriptor

        public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()

      • internalGetFieldAccessorTable

        protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
        Specified by:
        internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<CommonTlsContext.Builder>

      • clear

        public CommonTlsContext.Builder clear()
        Specified by:
        clear in interface com.google.protobuf.Message.Builder
        Specified by:
        clear in interface com.google.protobuf.MessageLite.Builder
        Overrides:
        clear in class com.google.protobuf.GeneratedMessageV3.Builder<CommonTlsContext.Builder>

      • getDescriptorForType

        public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
        Specified by:
        getDescriptorForType in interface com.google.protobuf.Message.Builder
        Specified by:
        getDescriptorForType in interface com.google.protobuf.MessageOrBuilder
        Overrides:
        getDescriptorForType in class com.google.protobuf.GeneratedMessageV3.Builder<CommonTlsContext.Builder>

      • getDefaultInstanceForType

        public CommonTlsContext getDefaultInstanceForType()
        Specified by:
        getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
        Specified by:
        getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder

      • build

        public CommonTlsContext build()
        Specified by:
        build in interface com.google.protobuf.Message.Builder
        Specified by:
        build in interface com.google.protobuf.MessageLite.Builder

      • buildPartial

        public CommonTlsContext buildPartial()
        Specified by:
        buildPartial in interface com.google.protobuf.Message.Builder
        Specified by:
        buildPartial in interface com.google.protobuf.MessageLite.Builder

      • clone

        public CommonTlsContext.Builder clone()
        Specified by:
        clone in interface com.google.protobuf.Message.Builder
        Specified by:
        clone in interface com.google.protobuf.MessageLite.Builder
        Overrides:
        clone in class com.google.protobuf.GeneratedMessageV3.Builder<CommonTlsContext.Builder>

      • setField

        public CommonTlsContext.Builder setField​(com.google.protobuf.Descriptors.FieldDescriptor field,
                                         Object value)
        Specified by:
        setField in interface com.google.protobuf.Message.Builder
        Overrides:
        setField in class com.google.protobuf.GeneratedMessageV3.Builder<CommonTlsContext.Builder>

      • clearField

        public CommonTlsContext.Builder clearField​(com.google.protobuf.Descriptors.FieldDescriptor field)
        Specified by:
        clearField in interface com.google.protobuf.Message.Builder
        Overrides:
        clearField in class com.google.protobuf.GeneratedMessageV3.Builder<CommonTlsContext.Builder>

      • clearOneof

        public CommonTlsContext.Builder clearOneof​(com.google.protobuf.Descriptors.OneofDescriptor oneof)
        Specified by:
        clearOneof in interface com.google.protobuf.Message.Builder
        Overrides:
        clearOneof in class com.google.protobuf.GeneratedMessageV3.Builder<CommonTlsContext.Builder>

      • setRepeatedField

        public CommonTlsContext.Builder setRepeatedField​(com.google.protobuf.Descriptors.FieldDescriptor field,
                                                 int index,
                                                 Object value)
        Specified by:
        setRepeatedField in interface com.google.protobuf.Message.Builder
        Overrides:
        setRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<CommonTlsContext.Builder>

      • addRepeatedField

        public CommonTlsContext.Builder addRepeatedField​(com.google.protobuf.Descriptors.FieldDescriptor field,
                                                 Object value)
        Specified by:
        addRepeatedField in interface com.google.protobuf.Message.Builder
        Overrides:
        addRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<CommonTlsContext.Builder>

      • mergeFrom

        public CommonTlsContext.Builder mergeFrom​(com.google.protobuf.Message other)
        Specified by:
        mergeFrom in interface com.google.protobuf.Message.Builder
        Overrides:
        mergeFrom in class com.google.protobuf.AbstractMessage.Builder<CommonTlsContext.Builder>

      • isInitialized

        public final boolean isInitialized()
        Specified by:
        isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
        Overrides:
        isInitialized in class com.google.protobuf.GeneratedMessageV3.Builder<CommonTlsContext.Builder>

      • mergeFrom

        public CommonTlsContext.Builder mergeFrom​(com.google.protobuf.CodedInputStream input,
                                          com.google.protobuf.ExtensionRegistryLite extensionRegistry)
                                   throws IOException
        Specified by:
        mergeFrom in interface com.google.protobuf.Message.Builder
        Specified by:
        mergeFrom in interface com.google.protobuf.MessageLite.Builder
        Overrides:
        mergeFrom in class com.google.protobuf.AbstractMessage.Builder<CommonTlsContext.Builder>
        Throws:
        IOException

      • hasTlsParams

        public boolean hasTlsParams()
         TLS protocol versions, cipher suites etc.
        .envoy.extensions.transport_sockets.tls.v3.TlsParameters tls_params = 1;
        Specified by:
        hasTlsParams in interface CommonTlsContextOrBuilder
        Returns:
        Whether the tlsParams field is set.

      • getTlsParams

        public TlsParameters getTlsParams()
         TLS protocol versions, cipher suites etc.
        .envoy.extensions.transport_sockets.tls.v3.TlsParameters tls_params = 1;
        Specified by:
        getTlsParams in interface CommonTlsContextOrBuilder
        Returns:
        The tlsParams.

      • setTlsParams

        public CommonTlsContext.Builder setTlsParams​(TlsParameters value)
         TLS protocol versions, cipher suites etc.
        .envoy.extensions.transport_sockets.tls.v3.TlsParameters tls_params = 1;

      • mergeTlsParams

        public CommonTlsContext.Builder mergeTlsParams​(TlsParameters value)
         TLS protocol versions, cipher suites etc.
        .envoy.extensions.transport_sockets.tls.v3.TlsParameters tls_params = 1;

      • clearTlsParams

        public CommonTlsContext.Builder clearTlsParams()
         TLS protocol versions, cipher suites etc.
        .envoy.extensions.transport_sockets.tls.v3.TlsParameters tls_params = 1;

      • getTlsParamsBuilder

        public TlsParameters.Builder getTlsParamsBuilder()
         TLS protocol versions, cipher suites etc.
        .envoy.extensions.transport_sockets.tls.v3.TlsParameters tls_params = 1;

      • getTlsCertificatesList

        public 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;
        Specified by:
        getTlsCertificatesList in interface CommonTlsContextOrBuilder

      • getTlsCertificatesCount

        public 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;
        Specified by:
        getTlsCertificatesCount in interface CommonTlsContextOrBuilder

      • getTlsCertificates

        public 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;
        Specified by:
        getTlsCertificates in interface CommonTlsContextOrBuilder

      • setTlsCertificates

        public CommonTlsContext.Builder setTlsCertificates​(int index,
                                                   TlsCertificate value)
         :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;

      • setTlsCertificates

        public CommonTlsContext.Builder setTlsCertificates​(int index,
                                                   TlsCertificate.Builder builderForValue)
         :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;

      • addTlsCertificates

        public CommonTlsContext.Builder addTlsCertificates​(TlsCertificate value)
         :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;

      • addTlsCertificates

        public CommonTlsContext.Builder addTlsCertificates​(int index,
                                                   TlsCertificate value)
         :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;

      • addTlsCertificates

        public CommonTlsContext.Builder addTlsCertificates​(TlsCertificate.Builder builderForValue)
         :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;

      • addTlsCertificates

        public CommonTlsContext.Builder addTlsCertificates​(int index,
                                                   TlsCertificate.Builder builderForValue)
         :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;

      • addAllTlsCertificates

        public CommonTlsContext.Builder addAllTlsCertificates​(Iterable<? extends TlsCertificate> values)
         :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;

      • clearTlsCertificates

        public CommonTlsContext.Builder clearTlsCertificates()
         :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;

      • removeTlsCertificates

        public CommonTlsContext.Builder removeTlsCertificates​(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;

      • getTlsCertificatesBuilder

        public TlsCertificate.Builder getTlsCertificatesBuilder​(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;

      • getTlsCertificatesOrBuilder

        public 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;
        Specified by:
        getTlsCertificatesOrBuilder in interface CommonTlsContextOrBuilder

      • getTlsCertificatesOrBuilderList

        public 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;
        Specified by:
        getTlsCertificatesOrBuilderList in interface CommonTlsContextOrBuilder

      • addTlsCertificatesBuilder

        public TlsCertificate.Builder addTlsCertificatesBuilder()
         :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;

      • addTlsCertificatesBuilder

        public TlsCertificate.Builder addTlsCertificatesBuilder​(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;

      • getTlsCertificatesBuilderList

        public List<TlsCertificate.Builder> getTlsCertificatesBuilderList()
         :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

        public 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) = { ... }
        Specified by:
        getTlsCertificateSdsSecretConfigsList in interface CommonTlsContextOrBuilder

      • getTlsCertificateSdsSecretConfigsCount

        public 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) = { ... }
        Specified by:
        getTlsCertificateSdsSecretConfigsCount in interface CommonTlsContextOrBuilder

      • getTlsCertificateSdsSecretConfigs

        public 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) = { ... }
        Specified by:
        getTlsCertificateSdsSecretConfigs in interface CommonTlsContextOrBuilder

      • setTlsCertificateSdsSecretConfigs

        public CommonTlsContext.Builder setTlsCertificateSdsSecretConfigs​(int index,
                                                                  SdsSecretConfig value)
         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) = { ... }

      • setTlsCertificateSdsSecretConfigs

        public CommonTlsContext.Builder setTlsCertificateSdsSecretConfigs​(int index,
                                                                  SdsSecretConfig.Builder builderForValue)
         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) = { ... }

      • addTlsCertificateSdsSecretConfigs

        public CommonTlsContext.Builder addTlsCertificateSdsSecretConfigs​(SdsSecretConfig value)
         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) = { ... }

      • addTlsCertificateSdsSecretConfigs

        public CommonTlsContext.Builder addTlsCertificateSdsSecretConfigs​(int index,
                                                                  SdsSecretConfig value)
         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) = { ... }

      • addTlsCertificateSdsSecretConfigs

        public CommonTlsContext.Builder addTlsCertificateSdsSecretConfigs​(SdsSecretConfig.Builder builderForValue)
         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) = { ... }

      • addTlsCertificateSdsSecretConfigs

        public CommonTlsContext.Builder addTlsCertificateSdsSecretConfigs​(int index,
                                                                  SdsSecretConfig.Builder builderForValue)
         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) = { ... }

      • addAllTlsCertificateSdsSecretConfigs

        public CommonTlsContext.Builder addAllTlsCertificateSdsSecretConfigs​(Iterable<? extends SdsSecretConfig> values)
         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) = { ... }

      • clearTlsCertificateSdsSecretConfigs

        public CommonTlsContext.Builder clearTlsCertificateSdsSecretConfigs()
         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) = { ... }

      • removeTlsCertificateSdsSecretConfigs

        public CommonTlsContext.Builder removeTlsCertificateSdsSecretConfigs​(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) = { ... }

      • getTlsCertificateSdsSecretConfigsBuilder

        public SdsSecretConfig.Builder getTlsCertificateSdsSecretConfigsBuilder​(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) = { ... }

      • getTlsCertificateSdsSecretConfigsOrBuilder

        public 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) = { ... }
        Specified by:
        getTlsCertificateSdsSecretConfigsOrBuilder in interface CommonTlsContextOrBuilder

      • getTlsCertificateSdsSecretConfigsOrBuilderList

        public 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) = { ... }
        Specified by:
        getTlsCertificateSdsSecretConfigsOrBuilderList in interface CommonTlsContextOrBuilder

      • addTlsCertificateSdsSecretConfigsBuilder

        public SdsSecretConfig.Builder addTlsCertificateSdsSecretConfigsBuilder()
         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) = { ... }

      • addTlsCertificateSdsSecretConfigsBuilder

        public SdsSecretConfig.Builder addTlsCertificateSdsSecretConfigsBuilder​(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) = { ... }

      • getTlsCertificateSdsSecretConfigsBuilderList

        public List<SdsSecretConfig.Builder> getTlsCertificateSdsSecretConfigsBuilderList()
         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

        public 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;
        Specified by:
        hasTlsCertificateProviderInstance in interface CommonTlsContextOrBuilder
        Returns:
        Whether the tlsCertificateProviderInstance field is set.

      • getTlsCertificateProviderInstance

        public 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;
        Specified by:
        getTlsCertificateProviderInstance in interface CommonTlsContextOrBuilder
        Returns:
        The tlsCertificateProviderInstance.

      • setTlsCertificateProviderInstance

        public CommonTlsContext.Builder setTlsCertificateProviderInstance​(CertificateProviderPluginInstance value)
         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;

      • setTlsCertificateProviderInstance

        public CommonTlsContext.Builder setTlsCertificateProviderInstance​(CertificateProviderPluginInstance.Builder builderForValue)
         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;

      • mergeTlsCertificateProviderInstance

        public CommonTlsContext.Builder mergeTlsCertificateProviderInstance​(CertificateProviderPluginInstance value)
         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;

      • clearTlsCertificateProviderInstance

        public CommonTlsContext.Builder clearTlsCertificateProviderInstance()
         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;

      • getTlsCertificateProviderInstanceBuilder

        public CertificateProviderPluginInstance.Builder getTlsCertificateProviderInstanceBuilder()
         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

        public 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;
        Specified by:
        getTlsCertificateProviderInstanceOrBuilder in interface CommonTlsContextOrBuilder

      • hasTlsCertificateCertificateProvider

        @Deprecated
public boolean hasTlsCertificateCertificateProvider()
        Deprecated.
        envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.tls_certificate_certificate_provider is deprecated. See envoy/extensions/transport_sockets/tls/v3/tls.proto;l=266
         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"];
        Specified by:
        hasTlsCertificateCertificateProvider in interface CommonTlsContextOrBuilder
        Returns:
        Whether the tlsCertificateCertificateProvider field is set.

      • getTlsCertificateCertificateProvider

        @Deprecated
public CommonTlsContext.CertificateProvider getTlsCertificateCertificateProvider()
        Deprecated.
        envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.tls_certificate_certificate_provider is deprecated. See envoy/extensions/transport_sockets/tls/v3/tls.proto;l=266
         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"];
        Specified by:
        getTlsCertificateCertificateProvider in interface CommonTlsContextOrBuilder
        Returns:
        The tlsCertificateCertificateProvider.

      • setTlsCertificateCertificateProvider

        @Deprecated
public CommonTlsContext.Builder setTlsCertificateCertificateProvider​(CommonTlsContext.CertificateProvider value)
        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"];

      • setTlsCertificateCertificateProvider

        @Deprecated
public CommonTlsContext.Builder setTlsCertificateCertificateProvider​(CommonTlsContext.CertificateProvider.Builder builderForValue)
        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"];

      • mergeTlsCertificateCertificateProvider

        @Deprecated
public CommonTlsContext.Builder mergeTlsCertificateCertificateProvider​(CommonTlsContext.CertificateProvider value)
        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"];

      • clearTlsCertificateCertificateProvider

        @Deprecated
public CommonTlsContext.Builder clearTlsCertificateCertificateProvider()
        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"];

      • getTlsCertificateCertificateProviderBuilder

        @Deprecated
public CommonTlsContext.CertificateProvider.Builder getTlsCertificateCertificateProviderBuilder()
        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
public boolean hasTlsCertificateCertificateProviderInstance()
        Deprecated.
        envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.tls_certificate_certificate_provider_instance is deprecated. See envoy/extensions/transport_sockets/tls/v3/tls.proto;l=271
         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"];
        Specified by:
        hasTlsCertificateCertificateProviderInstance in interface CommonTlsContextOrBuilder
        Returns:
        Whether the tlsCertificateCertificateProviderInstance field is set.

      • getTlsCertificateCertificateProviderInstance

        @Deprecated
public CommonTlsContext.CertificateProviderInstance getTlsCertificateCertificateProviderInstance()
        Deprecated.
        envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.tls_certificate_certificate_provider_instance is deprecated. See envoy/extensions/transport_sockets/tls/v3/tls.proto;l=271
         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"];
        Specified by:
        getTlsCertificateCertificateProviderInstance in interface CommonTlsContextOrBuilder
        Returns:
        The tlsCertificateCertificateProviderInstance.

      • setTlsCertificateCertificateProviderInstance

        @Deprecated
public CommonTlsContext.Builder setTlsCertificateCertificateProviderInstance​(CommonTlsContext.CertificateProviderInstance value)
        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"];

      • setTlsCertificateCertificateProviderInstance

        @Deprecated
public CommonTlsContext.Builder setTlsCertificateCertificateProviderInstance​(CommonTlsContext.CertificateProviderInstance.Builder builderForValue)
        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"];

      • mergeTlsCertificateCertificateProviderInstance

        @Deprecated
public CommonTlsContext.Builder mergeTlsCertificateCertificateProviderInstance​(CommonTlsContext.CertificateProviderInstance value)
        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"];

      • clearTlsCertificateCertificateProviderInstance

        @Deprecated
public CommonTlsContext.Builder clearTlsCertificateCertificateProviderInstance()
        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"];

      • getTlsCertificateCertificateProviderInstanceBuilder

        @Deprecated
public CommonTlsContext.CertificateProviderInstance.Builder getTlsCertificateCertificateProviderInstanceBuilder()
        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

        public boolean hasValidationContext()
         How to validate peer certificates.
        .envoy.extensions.transport_sockets.tls.v3.CertificateValidationContext validation_context = 3;
        Specified by:
        hasValidationContext in interface CommonTlsContextOrBuilder
        Returns:
        Whether the validationContext field is set.

      • clearValidationContext

        public CommonTlsContext.Builder clearValidationContext()
         How to validate peer certificates.
        .envoy.extensions.transport_sockets.tls.v3.CertificateValidationContext validation_context = 3;

      • getValidationContextBuilder

        public CertificateValidationContext.Builder getValidationContextBuilder()
         How to validate peer certificates.
        .envoy.extensions.transport_sockets.tls.v3.CertificateValidationContext validation_context = 3;

      • hasValidationContextSdsSecretConfig

        public 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;
        Specified by:
        hasValidationContextSdsSecretConfig in interface CommonTlsContextOrBuilder
        Returns:
        Whether the validationContextSdsSecretConfig field is set.

      • getValidationContextSdsSecretConfig

        public 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;
        Specified by:
        getValidationContextSdsSecretConfig in interface CommonTlsContextOrBuilder
        Returns:
        The validationContextSdsSecretConfig.

      • setValidationContextSdsSecretConfig

        public CommonTlsContext.Builder setValidationContextSdsSecretConfig​(SdsSecretConfig value)
         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;

      • setValidationContextSdsSecretConfig

        public CommonTlsContext.Builder setValidationContextSdsSecretConfig​(SdsSecretConfig.Builder builderForValue)
         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;

      • mergeValidationContextSdsSecretConfig

        public CommonTlsContext.Builder mergeValidationContextSdsSecretConfig​(SdsSecretConfig value)
         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;

      • clearValidationContextSdsSecretConfig

        public CommonTlsContext.Builder clearValidationContextSdsSecretConfig()
         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;

      • getValidationContextSdsSecretConfigBuilder

        public SdsSecretConfig.Builder getValidationContextSdsSecretConfigBuilder()
         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

        public 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;
        Specified by:
        getValidationContextSdsSecretConfigOrBuilder in interface CommonTlsContextOrBuilder

      • hasCombinedValidationContext

        public 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;
        Specified by:
        hasCombinedValidationContext in interface CommonTlsContextOrBuilder
        Returns:
        Whether the combinedValidationContext field is set.

      • getCombinedValidationContext

        public 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;
        Specified by:
        getCombinedValidationContext in interface CommonTlsContextOrBuilder
        Returns:
        The combinedValidationContext.

      • setCombinedValidationContext

        public CommonTlsContext.Builder setCombinedValidationContext​(CommonTlsContext.CombinedCertificateValidationContext value)
         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;

      • setCombinedValidationContext

        public CommonTlsContext.Builder setCombinedValidationContext​(CommonTlsContext.CombinedCertificateValidationContext.Builder builderForValue)
         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;

      • mergeCombinedValidationContext

        public CommonTlsContext.Builder mergeCombinedValidationContext​(CommonTlsContext.CombinedCertificateValidationContext value)
         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;

      • clearCombinedValidationContext

        public CommonTlsContext.Builder clearCombinedValidationContext()
         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;

      • getCombinedValidationContextBuilder

        public CommonTlsContext.CombinedCertificateValidationContext.Builder getCombinedValidationContextBuilder()
         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

        public 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;
        Specified by:
        getCombinedValidationContextOrBuilder in interface CommonTlsContextOrBuilder

      • hasValidationContextCertificateProvider

        @Deprecated
public boolean hasValidationContextCertificateProvider()
        Deprecated.
        envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.validation_context_certificate_provider is deprecated. See envoy/extensions/transport_sockets/tls/v3/tls.proto;l=293
         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"];
        Specified by:
        hasValidationContextCertificateProvider in interface CommonTlsContextOrBuilder
        Returns:
        Whether the validationContextCertificateProvider field is set.

      • getValidationContextCertificateProvider

        @Deprecated
public CommonTlsContext.CertificateProvider getValidationContextCertificateProvider()
        Deprecated.
        envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.validation_context_certificate_provider is deprecated. See envoy/extensions/transport_sockets/tls/v3/tls.proto;l=293
         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"];
        Specified by:
        getValidationContextCertificateProvider in interface CommonTlsContextOrBuilder
        Returns:
        The validationContextCertificateProvider.

      • setValidationContextCertificateProvider

        @Deprecated
public CommonTlsContext.Builder setValidationContextCertificateProvider​(CommonTlsContext.CertificateProvider value)
        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"];

      • setValidationContextCertificateProvider

        @Deprecated
public CommonTlsContext.Builder setValidationContextCertificateProvider​(CommonTlsContext.CertificateProvider.Builder builderForValue)
        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"];

      • mergeValidationContextCertificateProvider

        @Deprecated
public CommonTlsContext.Builder mergeValidationContextCertificateProvider​(CommonTlsContext.CertificateProvider value)
        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"];

      • clearValidationContextCertificateProvider

        @Deprecated
public CommonTlsContext.Builder clearValidationContextCertificateProvider()
        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"];

      • getValidationContextCertificateProviderBuilder

        @Deprecated
public CommonTlsContext.CertificateProvider.Builder getValidationContextCertificateProviderBuilder()
        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
public boolean hasValidationContextCertificateProviderInstance()
        Deprecated.
        envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.validation_context_certificate_provider_instance is deprecated. See envoy/extensions/transport_sockets/tls/v3/tls.proto;l=298
         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"];
        Specified by:
        hasValidationContextCertificateProviderInstance in interface CommonTlsContextOrBuilder
        Returns:
        Whether the validationContextCertificateProviderInstance field is set.

      • getValidationContextCertificateProviderInstance

        @Deprecated
public CommonTlsContext.CertificateProviderInstance getValidationContextCertificateProviderInstance()
        Deprecated.
        envoy.extensions.transport_sockets.tls.v3.CommonTlsContext.validation_context_certificate_provider_instance is deprecated. See envoy/extensions/transport_sockets/tls/v3/tls.proto;l=298
         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"];
        Specified by:
        getValidationContextCertificateProviderInstance in interface CommonTlsContextOrBuilder
        Returns:
        The validationContextCertificateProviderInstance.

      • setValidationContextCertificateProviderInstance

        @Deprecated
public CommonTlsContext.Builder setValidationContextCertificateProviderInstance​(CommonTlsContext.CertificateProviderInstance value)
        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"];

      • setValidationContextCertificateProviderInstance

        @Deprecated
public CommonTlsContext.Builder setValidationContextCertificateProviderInstance​(CommonTlsContext.CertificateProviderInstance.Builder builderForValue)
        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"];

      • mergeValidationContextCertificateProviderInstance

        @Deprecated
public CommonTlsContext.Builder mergeValidationContextCertificateProviderInstance​(CommonTlsContext.CertificateProviderInstance value)
        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"];

      • clearValidationContextCertificateProviderInstance

        @Deprecated
public CommonTlsContext.Builder clearValidationContextCertificateProviderInstance()
        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"];

      • getValidationContextCertificateProviderInstanceBuilder

        @Deprecated
public CommonTlsContext.CertificateProviderInstance.Builder getValidationContextCertificateProviderInstanceBuilder()
        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

        public com.google.protobuf.ProtocolStringList 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;
        Specified by:
        getAlpnProtocolsList in interface CommonTlsContextOrBuilder
        Returns:
        A list containing the alpnProtocols.

      • getAlpnProtocolsCount

        public 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;
        Specified by:
        getAlpnProtocolsCount in interface CommonTlsContextOrBuilder
        Returns:
        The count of alpnProtocols.

      • getAlpnProtocols

        public 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;
        Specified by:
        getAlpnProtocols in interface CommonTlsContextOrBuilder
        Parameters:
        index - The index of the element to return.
        Returns:
        The alpnProtocols at the given index.

      • getAlpnProtocolsBytes

        public 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;
        Specified by:
        getAlpnProtocolsBytes in interface CommonTlsContextOrBuilder
        Parameters:
        index - The index of the value to return.
        Returns:
        The bytes of the alpnProtocols at the given index.

      • setAlpnProtocols

        public CommonTlsContext.Builder setAlpnProtocols​(int index,
                                                 String value)
         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;
        Parameters:
        index - The index to set the value at.
        value - The alpnProtocols to set.
        Returns:
        This builder for chaining.

      • addAlpnProtocols

        public CommonTlsContext.Builder addAlpnProtocols​(String value)
         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;
        Parameters:
        value - The alpnProtocols to add.
        Returns:
        This builder for chaining.

      • addAllAlpnProtocols

        public CommonTlsContext.Builder addAllAlpnProtocols​(Iterable<String> values)
         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;
        Parameters:
        values - The alpnProtocols to add.
        Returns:
        This builder for chaining.

      • clearAlpnProtocols

        public CommonTlsContext.Builder clearAlpnProtocols()
         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;
        Returns:
        This builder for chaining.

      • addAlpnProtocolsBytes

        public CommonTlsContext.Builder addAlpnProtocolsBytes​(com.google.protobuf.ByteString value)
         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;
        Parameters:
        value - The bytes of the alpnProtocols to add.
        Returns:
        This builder for chaining.

      • hasCustomHandshaker

        public boolean hasCustomHandshaker()
         Custom TLS handshaker. If empty, defaults to native TLS handshaking
 behavior.
        .envoy.config.core.v3.TypedExtensionConfig custom_handshaker = 13;
        Specified by:
        hasCustomHandshaker in interface CommonTlsContextOrBuilder
        Returns:
        Whether the customHandshaker field is set.

      • getCustomHandshaker

        public TypedExtensionConfig getCustomHandshaker()
         Custom TLS handshaker. If empty, defaults to native TLS handshaking
 behavior.
        .envoy.config.core.v3.TypedExtensionConfig custom_handshaker = 13;
        Specified by:
        getCustomHandshaker in interface CommonTlsContextOrBuilder
        Returns:
        The customHandshaker.

      • setCustomHandshaker

        public CommonTlsContext.Builder setCustomHandshaker​(TypedExtensionConfig value)
         Custom TLS handshaker. If empty, defaults to native TLS handshaking
 behavior.
        .envoy.config.core.v3.TypedExtensionConfig custom_handshaker = 13;

      • setCustomHandshaker

        public CommonTlsContext.Builder setCustomHandshaker​(TypedExtensionConfig.Builder builderForValue)
         Custom TLS handshaker. If empty, defaults to native TLS handshaking
 behavior.
        .envoy.config.core.v3.TypedExtensionConfig custom_handshaker = 13;

      • mergeCustomHandshaker

        public CommonTlsContext.Builder mergeCustomHandshaker​(TypedExtensionConfig value)
         Custom TLS handshaker. If empty, defaults to native TLS handshaking
 behavior.
        .envoy.config.core.v3.TypedExtensionConfig custom_handshaker = 13;

      • clearCustomHandshaker

        public CommonTlsContext.Builder clearCustomHandshaker()
         Custom TLS handshaker. If empty, defaults to native TLS handshaking
 behavior.
        .envoy.config.core.v3.TypedExtensionConfig custom_handshaker = 13;

      • getCustomHandshakerBuilder

        public TypedExtensionConfig.Builder getCustomHandshakerBuilder()
         Custom TLS handshaker. If empty, defaults to native TLS handshaking
 behavior.
        .envoy.config.core.v3.TypedExtensionConfig custom_handshaker = 13;

      • hasKeyLog

        public boolean hasKeyLog()
         TLS key log configuration
        .envoy.extensions.transport_sockets.tls.v3.TlsKeyLog key_log = 15;
        Specified by:
        hasKeyLog in interface CommonTlsContextOrBuilder
        Returns:
        Whether the keyLog field is set.

      • getKeyLog

        public TlsKeyLog getKeyLog()
         TLS key log configuration
        .envoy.extensions.transport_sockets.tls.v3.TlsKeyLog key_log = 15;
        Specified by:
        getKeyLog in interface CommonTlsContextOrBuilder
        Returns:
        The keyLog.

      • setKeyLog

        public CommonTlsContext.Builder setKeyLog​(TlsKeyLog value)
         TLS key log configuration
        .envoy.extensions.transport_sockets.tls.v3.TlsKeyLog key_log = 15;

      • mergeKeyLog

        public CommonTlsContext.Builder mergeKeyLog​(TlsKeyLog value)
         TLS key log configuration
        .envoy.extensions.transport_sockets.tls.v3.TlsKeyLog key_log = 15;

      • clearKeyLog

        public CommonTlsContext.Builder clearKeyLog()
         TLS key log configuration
        .envoy.extensions.transport_sockets.tls.v3.TlsKeyLog key_log = 15;

      • getKeyLogBuilder

        public TlsKeyLog.Builder getKeyLogBuilder()
         TLS key log configuration
        .envoy.extensions.transport_sockets.tls.v3.TlsKeyLog key_log = 15;

      • setUnknownFields

        public final CommonTlsContext.Builder setUnknownFields​(com.google.protobuf.UnknownFieldSet unknownFields)
        Specified by:
        setUnknownFields in interface com.google.protobuf.Message.Builder
        Overrides:
        setUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<CommonTlsContext.Builder>

      • mergeUnknownFields

        public final CommonTlsContext.Builder mergeUnknownFields​(com.google.protobuf.UnknownFieldSet unknownFields)
        Specified by:
        mergeUnknownFields in interface com.google.protobuf.Message.Builder
        Overrides:
        mergeUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<CommonTlsContext.Builder>