All Downloads are FREE. Search and download functionalities are using the official Maven repository.

io.envoyproxy.envoy.api.v2.auth.CommonTlsContextOrBuilder Maven / Gradle / Ivy

The newest version!
// Generated by the protocol buffer compiler.  DO NOT EDIT!
// source: envoy/api/v2/auth/tls.proto

package io.envoyproxy.envoy.api.v2.auth;

public interface CommonTlsContextOrBuilder extends
    // @@protoc_insertion_point(interface_extends:envoy.api.v2.auth.CommonTlsContext)
    com.google.protobuf.MessageOrBuilder {

  /**
   * 
   * TLS protocol versions, cipher suites etc.
   * 
* * .envoy.api.v2.auth.TlsParameters tls_params = 1; * @return Whether the tlsParams field is set. */ boolean hasTlsParams(); /** *
   * TLS protocol versions, cipher suites etc.
   * 
* * .envoy.api.v2.auth.TlsParameters tls_params = 1; * @return The tlsParams. */ io.envoyproxy.envoy.api.v2.auth.TlsParameters getTlsParams(); /** *
   * TLS protocol versions, cipher suites etc.
   * 
* * .envoy.api.v2.auth.TlsParameters tls_params = 1; */ io.envoyproxy.envoy.api.v2.auth.TlsParametersOrBuilder getTlsParamsOrBuilder(); /** *
   * :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.
   * 
* * repeated .envoy.api.v2.auth.TlsCertificate tls_certificates = 2; */ java.util.List 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.
   * 
* * repeated .envoy.api.v2.auth.TlsCertificate tls_certificates = 2; */ io.envoyproxy.envoy.api.v2.auth.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.
   * 
* * repeated .envoy.api.v2.auth.TlsCertificate tls_certificates = 2; */ 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.
   * 
* * repeated .envoy.api.v2.auth.TlsCertificate tls_certificates = 2; */ java.util.List 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.
   * 
* * repeated .envoy.api.v2.auth.TlsCertificate tls_certificates = 2; */ io.envoyproxy.envoy.api.v2.auth.TlsCertificateOrBuilder getTlsCertificatesOrBuilder( int index); /** *
   * Configs for fetching TLS certificates via SDS API.
   * 
* * repeated .envoy.api.v2.auth.SdsSecretConfig tls_certificate_sds_secret_configs = 6 [(.validate.rules) = { ... } */ java.util.List getTlsCertificateSdsSecretConfigsList(); /** *
   * Configs for fetching TLS certificates via SDS API.
   * 
* * repeated .envoy.api.v2.auth.SdsSecretConfig tls_certificate_sds_secret_configs = 6 [(.validate.rules) = { ... } */ io.envoyproxy.envoy.api.v2.auth.SdsSecretConfig getTlsCertificateSdsSecretConfigs(int index); /** *
   * Configs for fetching TLS certificates via SDS API.
   * 
* * repeated .envoy.api.v2.auth.SdsSecretConfig tls_certificate_sds_secret_configs = 6 [(.validate.rules) = { ... } */ int getTlsCertificateSdsSecretConfigsCount(); /** *
   * Configs for fetching TLS certificates via SDS API.
   * 
* * repeated .envoy.api.v2.auth.SdsSecretConfig tls_certificate_sds_secret_configs = 6 [(.validate.rules) = { ... } */ java.util.List getTlsCertificateSdsSecretConfigsOrBuilderList(); /** *
   * Configs for fetching TLS certificates via SDS API.
   * 
* * repeated .envoy.api.v2.auth.SdsSecretConfig tls_certificate_sds_secret_configs = 6 [(.validate.rules) = { ... } */ io.envoyproxy.envoy.api.v2.auth.SdsSecretConfigOrBuilder getTlsCertificateSdsSecretConfigsOrBuilder( int index); /** *
   * How to validate peer certificates.
   * 
* * .envoy.api.v2.auth.CertificateValidationContext validation_context = 3; * @return Whether the validationContext field is set. */ boolean hasValidationContext(); /** *
   * How to validate peer certificates.
   * 
* * .envoy.api.v2.auth.CertificateValidationContext validation_context = 3; * @return The validationContext. */ io.envoyproxy.envoy.api.v2.auth.CertificateValidationContext getValidationContext(); /** *
   * How to validate peer certificates.
   * 
* * .envoy.api.v2.auth.CertificateValidationContext validation_context = 3; */ io.envoyproxy.envoy.api.v2.auth.CertificateValidationContextOrBuilder getValidationContextOrBuilder(); /** *
   * Config for fetching validation context via SDS API.
   * 
* * .envoy.api.v2.auth.SdsSecretConfig validation_context_sds_secret_config = 7; * @return Whether the validationContextSdsSecretConfig field is set. */ boolean hasValidationContextSdsSecretConfig(); /** *
   * Config for fetching validation context via SDS API.
   * 
* * .envoy.api.v2.auth.SdsSecretConfig validation_context_sds_secret_config = 7; * @return The validationContextSdsSecretConfig. */ io.envoyproxy.envoy.api.v2.auth.SdsSecretConfig getValidationContextSdsSecretConfig(); /** *
   * Config for fetching validation context via SDS API.
   * 
* * .envoy.api.v2.auth.SdsSecretConfig validation_context_sds_secret_config = 7; */ io.envoyproxy.envoy.api.v2.auth.SdsSecretConfigOrBuilder getValidationContextSdsSecretConfigOrBuilder(); /** *
   * 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.api.v2.auth.CommonTlsContext.CombinedCertificateValidationContext combined_validation_context = 8; * @return Whether the combinedValidationContext field is set. */ 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.api.v2.auth.CommonTlsContext.CombinedCertificateValidationContext combined_validation_context = 8; * @return The combinedValidationContext. */ io.envoyproxy.envoy.api.v2.auth.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.api.v2.auth.CommonTlsContext.CombinedCertificateValidationContext combined_validation_context = 8; */ io.envoyproxy.envoy.api.v2.auth.CommonTlsContext.CombinedCertificateValidationContextOrBuilder getCombinedValidationContextOrBuilder(); /** *
   * 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_api_field_config.filter.network.http_connection_manager.v2.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; * @return A list containing the alpnProtocols. */ java.util.List 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_api_field_config.filter.network.http_connection_manager.v2.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; * @return The count of alpnProtocols. */ 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_api_field_config.filter.network.http_connection_manager.v2.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; * @param index The index of the element to return. * @return The alpnProtocols at the given index. */ java.lang.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_api_field_config.filter.network.http_connection_manager.v2.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; * @param index The index of the value to return. * @return The bytes of the alpnProtocols at the given index. */ com.google.protobuf.ByteString getAlpnProtocolsBytes(int index); public io.envoyproxy.envoy.api.v2.auth.CommonTlsContext.ValidationContextTypeCase getValidationContextTypeCase(); }




© 2015 - 2025 Weber Informatics LLC | Privacy Policy