Class JwtProvider.Builder
java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderT>
com.google.protobuf.GeneratedMessageV3.Builder<JwtProvider.Builder>
io.envoyproxy.envoy.extensions.filters.http.jwt_authn.v3.JwtProvider.Builder
- All Implemented Interfaces:
com.google.protobuf.Message.Builder,com.google.protobuf.MessageLite.Builder,com.google.protobuf.MessageLiteOrBuilder,com.google.protobuf.MessageOrBuilder,JwtProviderOrBuilder,Cloneable
- Enclosing class:
- JwtProvider
public static final class JwtProvider.Builder
extends com.google.protobuf.GeneratedMessageV3.Builder<JwtProvider.Builder>
implements JwtProviderOrBuilder
Please see following for JWT authentication flow:
* `JSON Web Token (JWT) <https://tools.ietf.org/html/rfc7519>`_
* `The OAuth 2.0 Authorization Framework <https://tools.ietf.org/html/rfc6749>`_
* `OpenID Connect <http://openid.net/connect>`_
A JwtProvider message specifies how a JSON Web Token (JWT) can be verified. It specifies:
* issuer: the principal that issues the JWT. If specified, it has to match the ``iss`` field in JWT.
* allowed audiences: the ones in the token have to be listed here.
* how to fetch public key JWKS to verify the token signature.
* how to extract the JWT in the request.
* how to pass successfully verified token payload.
Example:
.. code-block:: yaml
issuer: https://example.com
audiences:
- bookstore_android.apps.googleusercontent.com
- bookstore_web.apps.googleusercontent.com
remote_jwks:
http_uri:
uri: https://example.com/.well-known/jwks.json
cluster: example_jwks_cluster
timeout: 1s
cache_duration:
seconds: 300
[#next-free-field: 22]
Protobuf type envoy.extensions.filters.http.jwt_authn.v3.JwtProvider-
Method Summary
Modifier and TypeMethodDescriptionaddAllAudiences(Iterable<String> values) The list of JWT `audiences <https://tools.ietf.org/html/rfc7519#section-4.1.3>`_ are allowed to access.addAllClaimToHeaders(Iterable<? extends JwtClaimToHeader> values) Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header.addAllFromCookies(Iterable<String> values) JWT is sent in a cookie.addAllFromHeaders(Iterable<? extends JwtHeader> values) Two fields below define where to extract the JWT from an HTTP request.addAllFromParams(Iterable<String> values) JWT is sent in a query parameter.addAudiences(String value) The list of JWT `audiences <https://tools.ietf.org/html/rfc7519#section-4.1.3>`_ are allowed to access.addAudiencesBytes(com.google.protobuf.ByteString value) The list of JWT `audiences <https://tools.ietf.org/html/rfc7519#section-4.1.3>`_ are allowed to access.addClaimToHeaders(int index, JwtClaimToHeader value) Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header.addClaimToHeaders(int index, JwtClaimToHeader.Builder builderForValue) Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header.Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header.addClaimToHeaders(JwtClaimToHeader.Builder builderForValue) Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header.Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header.addClaimToHeadersBuilder(int index) Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header.addFromCookies(String value) JWT is sent in a cookie.addFromCookiesBytes(com.google.protobuf.ByteString value) JWT is sent in a cookie.addFromHeaders(int index, JwtHeader value) Two fields below define where to extract the JWT from an HTTP request.addFromHeaders(int index, JwtHeader.Builder builderForValue) Two fields below define where to extract the JWT from an HTTP request.addFromHeaders(JwtHeader value) Two fields below define where to extract the JWT from an HTTP request.addFromHeaders(JwtHeader.Builder builderForValue) Two fields below define where to extract the JWT from an HTTP request.Two fields below define where to extract the JWT from an HTTP request.addFromHeadersBuilder(int index) Two fields below define where to extract the JWT from an HTTP request.addFromParams(String value) JWT is sent in a query parameter.addFromParamsBytes(com.google.protobuf.ByteString value) JWT is sent in a query parameter.addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value) build()clear()The list of JWT `audiences <https://tools.ietf.org/html/rfc7519#section-4.1.3>`_ are allowed to access.Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header.Clears route cache in order to allow the JWT to correctly affect routing decisions.Specify the clock skew in seconds when verifying JWT time constraint, such as ``exp``, and ``nbf``.If non empty, the failure status ``::google::jwt_verify::Status`` for a non verified JWT will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ``envoy.filters.http.jwt_authn`` The value is the ``protobuf::Struct``.clearField(com.google.protobuf.Descriptors.FieldDescriptor field) If false, the JWT is removed in the request after a success verification.This field specifies the header name to forward a successfully verified JWT payload to the backend.JWT is sent in a cookie.Two fields below define where to extract the JWT from an HTTP request.JWT is sent in a query parameter.If not empty, similar to :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>`, a successfully verified JWT header will be written to :ref:`Dynamic State <arch_overview_data_sharing_between_filters>` as an entry (``protobuf::Struct``) in ``envoy.filters.http.jwt_authn`` ``namespace`` with the value of this field as the key.Specify the `principal <https://tools.ietf.org/html/rfc7519#section-4.1.1>`_ that issued the JWT, usually a URL or an email address.Enables JWT cache, its size is specified by ``jwt_cache_size``.JWKS is in local data source.Restrict the maximum remaining lifetime of a credential from the JwtProvider.Normalizes the payload representation in the request metadata.clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof) When :ref:`forward_payload_header <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.forward_payload_header>` is specified, the base64 encoded payload will be added to the headers.If non empty, successfully verified JWT payloads will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ````envoy.filters.http.jwt_authn```` The value is the ``protobuf::Struct``.JWKS can be fetched from remote server via HTTP/HTTPS.Requires that the credential contains an `expiration <https://tools.ietf.org/html/rfc7519#section-4.1.4>`_.Restrict the `subjects <https://tools.ietf.org/html/rfc7519#section-4.1.2>`_ that the JwtProvider can assert.clone()getAudiences(int index) The list of JWT `audiences <https://tools.ietf.org/html/rfc7519#section-4.1.3>`_ are allowed to access.com.google.protobuf.ByteStringgetAudiencesBytes(int index) The list of JWT `audiences <https://tools.ietf.org/html/rfc7519#section-4.1.3>`_ are allowed to access.intThe list of JWT `audiences <https://tools.ietf.org/html/rfc7519#section-4.1.3>`_ are allowed to access.com.google.protobuf.ProtocolStringListThe list of JWT `audiences <https://tools.ietf.org/html/rfc7519#section-4.1.3>`_ are allowed to access.getClaimToHeaders(int index) Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header.getClaimToHeadersBuilder(int index) Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header.Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header.intAdd JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header.Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header.getClaimToHeadersOrBuilder(int index) Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header.List<? extends JwtClaimToHeaderOrBuilder>Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header.booleanClears route cache in order to allow the JWT to correctly affect routing decisions.intSpecify the clock skew in seconds when verifying JWT time constraint, such as ``exp``, and ``nbf``.static final com.google.protobuf.Descriptors.Descriptorcom.google.protobuf.Descriptors.DescriptorIf non empty, the failure status ``::google::jwt_verify::Status`` for a non verified JWT will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ``envoy.filters.http.jwt_authn`` The value is the ``protobuf::Struct``.com.google.protobuf.ByteStringIf non empty, the failure status ``::google::jwt_verify::Status`` for a non verified JWT will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ``envoy.filters.http.jwt_authn`` The value is the ``protobuf::Struct``.booleanIf false, the JWT is removed in the request after a success verification.This field specifies the header name to forward a successfully verified JWT payload to the backend.com.google.protobuf.ByteStringThis field specifies the header name to forward a successfully verified JWT payload to the backend.getFromCookies(int index) JWT is sent in a cookie.com.google.protobuf.ByteStringgetFromCookiesBytes(int index) JWT is sent in a cookie.intJWT is sent in a cookie.com.google.protobuf.ProtocolStringListJWT is sent in a cookie.getFromHeaders(int index) Two fields below define where to extract the JWT from an HTTP request.getFromHeadersBuilder(int index) Two fields below define where to extract the JWT from an HTTP request.Two fields below define where to extract the JWT from an HTTP request.intTwo fields below define where to extract the JWT from an HTTP request.Two fields below define where to extract the JWT from an HTTP request.getFromHeadersOrBuilder(int index) Two fields below define where to extract the JWT from an HTTP request.List<? extends JwtHeaderOrBuilder>Two fields below define where to extract the JWT from an HTTP request.getFromParams(int index) JWT is sent in a query parameter.com.google.protobuf.ByteStringgetFromParamsBytes(int index) JWT is sent in a query parameter.intJWT is sent in a query parameter.com.google.protobuf.ProtocolStringListJWT is sent in a query parameter.If not empty, similar to :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>`, a successfully verified JWT header will be written to :ref:`Dynamic State <arch_overview_data_sharing_between_filters>` as an entry (``protobuf::Struct``) in ``envoy.filters.http.jwt_authn`` ``namespace`` with the value of this field as the key.com.google.protobuf.ByteStringIf not empty, similar to :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>`, a successfully verified JWT header will be written to :ref:`Dynamic State <arch_overview_data_sharing_between_filters>` as an entry (``protobuf::Struct``) in ``envoy.filters.http.jwt_authn`` ``namespace`` with the value of this field as the key.Specify the `principal <https://tools.ietf.org/html/rfc7519#section-4.1.1>`_ that issued the JWT, usually a URL or an email address.com.google.protobuf.ByteStringSpecify the `principal <https://tools.ietf.org/html/rfc7519#section-4.1.1>`_ that issued the JWT, usually a URL or an email address.Enables JWT cache, its size is specified by ``jwt_cache_size``.Enables JWT cache, its size is specified by ``jwt_cache_size``.Enables JWT cache, its size is specified by ``jwt_cache_size``.JWKS is in local data source.JWKS is in local data source.JWKS is in local data source.com.google.protobuf.DurationRestrict the maximum remaining lifetime of a credential from the JwtProvider.com.google.protobuf.Duration.BuilderRestrict the maximum remaining lifetime of a credential from the JwtProvider.com.google.protobuf.DurationOrBuilderRestrict the maximum remaining lifetime of a credential from the JwtProvider.Normalizes the payload representation in the request metadata.Normalizes the payload representation in the request metadata.Normalizes the payload representation in the request metadata.booleanWhen :ref:`forward_payload_header <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.forward_payload_header>` is specified, the base64 encoded payload will be added to the headers.If non empty, successfully verified JWT payloads will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ````envoy.filters.http.jwt_authn```` The value is the ``protobuf::Struct``.com.google.protobuf.ByteStringIf non empty, successfully verified JWT payloads will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ````envoy.filters.http.jwt_authn```` The value is the ``protobuf::Struct``.JWKS can be fetched from remote server via HTTP/HTTPS.JWKS can be fetched from remote server via HTTP/HTTPS.JWKS can be fetched from remote server via HTTP/HTTPS.booleanRequires that the credential contains an `expiration <https://tools.ietf.org/html/rfc7519#section-4.1.4>`_.Restrict the `subjects <https://tools.ietf.org/html/rfc7519#section-4.1.2>`_ that the JwtProvider can assert.Restrict the `subjects <https://tools.ietf.org/html/rfc7519#section-4.1.2>`_ that the JwtProvider can assert.Restrict the `subjects <https://tools.ietf.org/html/rfc7519#section-4.1.2>`_ that the JwtProvider can assert.booleanEnables JWT cache, its size is specified by ``jwt_cache_size``.booleanJWKS is in local data source.booleanRestrict the maximum remaining lifetime of a credential from the JwtProvider.booleanNormalizes the payload representation in the request metadata.booleanJWKS can be fetched from remote server via HTTP/HTTPS.booleanRestrict the `subjects <https://tools.ietf.org/html/rfc7519#section-4.1.2>`_ that the JwtProvider can assert.protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTablefinal booleanmergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) mergeFrom(com.google.protobuf.Message other) mergeFrom(JwtProvider other) Enables JWT cache, its size is specified by ``jwt_cache_size``.mergeLocalJwks(DataSource value) JWKS is in local data source.mergeMaxLifetime(com.google.protobuf.Duration value) Restrict the maximum remaining lifetime of a credential from the JwtProvider.Normalizes the payload representation in the request metadata.mergeRemoteJwks(RemoteJwks value) JWKS can be fetched from remote server via HTTP/HTTPS.mergeSubjects(StringMatcher value) Restrict the `subjects <https://tools.ietf.org/html/rfc7519#section-4.1.2>`_ that the JwtProvider can assert.final JwtProvider.BuildermergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) removeClaimToHeaders(int index) Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header.removeFromHeaders(int index) Two fields below define where to extract the JWT from an HTTP request.setAudiences(int index, String value) The list of JWT `audiences <https://tools.ietf.org/html/rfc7519#section-4.1.3>`_ are allowed to access.setClaimToHeaders(int index, JwtClaimToHeader value) Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header.setClaimToHeaders(int index, JwtClaimToHeader.Builder builderForValue) Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header.setClearRouteCache(boolean value) Clears route cache in order to allow the JWT to correctly affect routing decisions.setClockSkewSeconds(int value) Specify the clock skew in seconds when verifying JWT time constraint, such as ``exp``, and ``nbf``.setFailedStatusInMetadata(String value) If non empty, the failure status ``::google::jwt_verify::Status`` for a non verified JWT will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ``envoy.filters.http.jwt_authn`` The value is the ``protobuf::Struct``.setFailedStatusInMetadataBytes(com.google.protobuf.ByteString value) If non empty, the failure status ``::google::jwt_verify::Status`` for a non verified JWT will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ``envoy.filters.http.jwt_authn`` The value is the ``protobuf::Struct``.setForward(boolean value) If false, the JWT is removed in the request after a success verification.setForwardPayloadHeader(String value) This field specifies the header name to forward a successfully verified JWT payload to the backend.setForwardPayloadHeaderBytes(com.google.protobuf.ByteString value) This field specifies the header name to forward a successfully verified JWT payload to the backend.setFromCookies(int index, String value) JWT is sent in a cookie.setFromHeaders(int index, JwtHeader value) Two fields below define where to extract the JWT from an HTTP request.setFromHeaders(int index, JwtHeader.Builder builderForValue) Two fields below define where to extract the JWT from an HTTP request.setFromParams(int index, String value) JWT is sent in a query parameter.setHeaderInMetadata(String value) If not empty, similar to :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>`, a successfully verified JWT header will be written to :ref:`Dynamic State <arch_overview_data_sharing_between_filters>` as an entry (``protobuf::Struct``) in ``envoy.filters.http.jwt_authn`` ``namespace`` with the value of this field as the key.setHeaderInMetadataBytes(com.google.protobuf.ByteString value) If not empty, similar to :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>`, a successfully verified JWT header will be written to :ref:`Dynamic State <arch_overview_data_sharing_between_filters>` as an entry (``protobuf::Struct``) in ``envoy.filters.http.jwt_authn`` ``namespace`` with the value of this field as the key.Specify the `principal <https://tools.ietf.org/html/rfc7519#section-4.1.1>`_ that issued the JWT, usually a URL or an email address.setIssuerBytes(com.google.protobuf.ByteString value) Specify the `principal <https://tools.ietf.org/html/rfc7519#section-4.1.1>`_ that issued the JWT, usually a URL or an email address.setJwtCacheConfig(JwtCacheConfig value) Enables JWT cache, its size is specified by ``jwt_cache_size``.setJwtCacheConfig(JwtCacheConfig.Builder builderForValue) Enables JWT cache, its size is specified by ``jwt_cache_size``.setLocalJwks(DataSource value) JWKS is in local data source.setLocalJwks(DataSource.Builder builderForValue) JWKS is in local data source.setMaxLifetime(com.google.protobuf.Duration value) Restrict the maximum remaining lifetime of a credential from the JwtProvider.setMaxLifetime(com.google.protobuf.Duration.Builder builderForValue) Restrict the maximum remaining lifetime of a credential from the JwtProvider.Normalizes the payload representation in the request metadata.setNormalizePayloadInMetadata(JwtProvider.NormalizePayload.Builder builderForValue) Normalizes the payload representation in the request metadata.setPadForwardPayloadHeader(boolean value) When :ref:`forward_payload_header <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.forward_payload_header>` is specified, the base64 encoded payload will be added to the headers.setPayloadInMetadata(String value) If non empty, successfully verified JWT payloads will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ````envoy.filters.http.jwt_authn```` The value is the ``protobuf::Struct``.setPayloadInMetadataBytes(com.google.protobuf.ByteString value) If non empty, successfully verified JWT payloads will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ````envoy.filters.http.jwt_authn```` The value is the ``protobuf::Struct``.setRemoteJwks(RemoteJwks value) JWKS can be fetched from remote server via HTTP/HTTPS.setRemoteJwks(RemoteJwks.Builder builderForValue) JWKS can be fetched from remote server via HTTP/HTTPS.setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value) setRequireExpiration(boolean value) Requires that the credential contains an `expiration <https://tools.ietf.org/html/rfc7519#section-4.1.4>`_.setSubjects(StringMatcher value) Restrict the `subjects <https://tools.ietf.org/html/rfc7519#section-4.1.2>`_ that the JwtProvider can assert.setSubjects(StringMatcher.Builder builderForValue) Restrict the `subjects <https://tools.ietf.org/html/rfc7519#section-4.1.2>`_ that the JwtProvider can assert.final JwtProvider.BuildersetUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) Methods inherited from class com.google.protobuf.GeneratedMessageV3.Builder
getAllFields, getField, getFieldBuilder, getOneofFieldDescriptor, getParentForChildren, getRepeatedField, getRepeatedFieldBuilder, getRepeatedFieldCount, getUnknownFields, getUnknownFieldSetBuilder, hasField, hasOneof, internalGetMapField, internalGetMapFieldReflection, internalGetMutableMapField, internalGetMutableMapFieldReflection, isClean, markClean, mergeUnknownLengthDelimitedField, mergeUnknownVarintField, newBuilderForField, onBuilt, onChanged, parseUnknownField, setUnknownFieldSetBuilder, setUnknownFieldsProto3Methods inherited from class com.google.protobuf.AbstractMessage.Builder
findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toStringMethods inherited from class com.google.protobuf.AbstractMessageLite.Builder
addAll, addAll, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, newUninitializedMessageExceptionMethods inherited from class java.lang.Object
equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitMethods inherited from interface com.google.protobuf.Message.Builder
mergeDelimitedFrom, mergeDelimitedFromMethods inherited from interface com.google.protobuf.MessageLite.Builder
mergeFromMethods inherited from interface com.google.protobuf.MessageOrBuilder
findInitializationErrors, getAllFields, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
-
Method Details
-
getDescriptor
public static final com.google.protobuf.Descriptors.Descriptor getDescriptor() -
internalGetFieldAccessorTable
protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()- Specified by:
internalGetFieldAccessorTablein classcom.google.protobuf.GeneratedMessageV3.Builder<JwtProvider.Builder>
-
clear
- Specified by:
clearin interfacecom.google.protobuf.Message.Builder- Specified by:
clearin interfacecom.google.protobuf.MessageLite.Builder- Overrides:
clearin classcom.google.protobuf.GeneratedMessageV3.Builder<JwtProvider.Builder>
-
getDescriptorForType
public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()- Specified by:
getDescriptorForTypein interfacecom.google.protobuf.Message.Builder- Specified by:
getDescriptorForTypein interfacecom.google.protobuf.MessageOrBuilder- Overrides:
getDescriptorForTypein classcom.google.protobuf.GeneratedMessageV3.Builder<JwtProvider.Builder>
-
getDefaultInstanceForType
- Specified by:
getDefaultInstanceForTypein interfacecom.google.protobuf.MessageLiteOrBuilder- Specified by:
getDefaultInstanceForTypein interfacecom.google.protobuf.MessageOrBuilder
-
build
- Specified by:
buildin interfacecom.google.protobuf.Message.Builder- Specified by:
buildin interfacecom.google.protobuf.MessageLite.Builder
-
buildPartial
- Specified by:
buildPartialin interfacecom.google.protobuf.Message.Builder- Specified by:
buildPartialin interfacecom.google.protobuf.MessageLite.Builder
-
clone
- Specified by:
clonein interfacecom.google.protobuf.Message.Builder- Specified by:
clonein interfacecom.google.protobuf.MessageLite.Builder- Overrides:
clonein classcom.google.protobuf.GeneratedMessageV3.Builder<JwtProvider.Builder>
-
setField
public JwtProvider.Builder setField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value) - Specified by:
setFieldin interfacecom.google.protobuf.Message.Builder- Overrides:
setFieldin classcom.google.protobuf.GeneratedMessageV3.Builder<JwtProvider.Builder>
-
clearField
- Specified by:
clearFieldin interfacecom.google.protobuf.Message.Builder- Overrides:
clearFieldin classcom.google.protobuf.GeneratedMessageV3.Builder<JwtProvider.Builder>
-
clearOneof
- Specified by:
clearOneofin interfacecom.google.protobuf.Message.Builder- Overrides:
clearOneofin classcom.google.protobuf.GeneratedMessageV3.Builder<JwtProvider.Builder>
-
setRepeatedField
public JwtProvider.Builder setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value) - Specified by:
setRepeatedFieldin interfacecom.google.protobuf.Message.Builder- Overrides:
setRepeatedFieldin classcom.google.protobuf.GeneratedMessageV3.Builder<JwtProvider.Builder>
-
addRepeatedField
public JwtProvider.Builder addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value) - Specified by:
addRepeatedFieldin interfacecom.google.protobuf.Message.Builder- Overrides:
addRepeatedFieldin classcom.google.protobuf.GeneratedMessageV3.Builder<JwtProvider.Builder>
-
mergeFrom
- Specified by:
mergeFromin interfacecom.google.protobuf.Message.Builder- Overrides:
mergeFromin classcom.google.protobuf.AbstractMessage.Builder<JwtProvider.Builder>
-
mergeFrom
-
isInitialized
public final boolean isInitialized()- Specified by:
isInitializedin interfacecom.google.protobuf.MessageLiteOrBuilder- Overrides:
isInitializedin classcom.google.protobuf.GeneratedMessageV3.Builder<JwtProvider.Builder>
-
mergeFrom
public JwtProvider.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException - Specified by:
mergeFromin interfacecom.google.protobuf.Message.Builder- Specified by:
mergeFromin interfacecom.google.protobuf.MessageLite.Builder- Overrides:
mergeFromin classcom.google.protobuf.AbstractMessage.Builder<JwtProvider.Builder>- Throws:
IOException
-
getJwksSourceSpecifierCase
- Specified by:
getJwksSourceSpecifierCasein interfaceJwtProviderOrBuilder
-
clearJwksSourceSpecifier
-
getIssuer
Specify the `principal <https://tools.ietf.org/html/rfc7519#section-4.1.1>`_ that issued the JWT, usually a URL or an email address. It is optional. If specified, it has to match the ``iss`` field in JWT, otherwise the JWT ``iss`` field is not checked. .. note:: ``JwtRequirement`` :ref:`allow_missing <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtRequirement.allow_missing>` and :ref:`allow_missing_or_failed <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtRequirement.allow_missing_or_failed>` are implemented differently than other ``JwtRequirements``. Hence the usage of this field is different as follows if ``allow_missing`` or ``allow_missing_or_failed`` is used: * If a JWT has ``iss`` field, it needs to be specified by this field in one of ``JwtProviders``. * If a JWT doesn't have ``iss`` field, one of ``JwtProviders`` should fill this field empty. * Multiple ``JwtProviders`` should not have same value in this field. Examples: * https://securetoken.google.com * Example: 1234567-compute@developer.gserviceaccount.comstring issuer = 1;- Specified by:
getIssuerin interfaceJwtProviderOrBuilder- Returns:
- The issuer.
-
getIssuerBytes
public com.google.protobuf.ByteString getIssuerBytes()Specify the `principal <https://tools.ietf.org/html/rfc7519#section-4.1.1>`_ that issued the JWT, usually a URL or an email address. It is optional. If specified, it has to match the ``iss`` field in JWT, otherwise the JWT ``iss`` field is not checked. .. note:: ``JwtRequirement`` :ref:`allow_missing <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtRequirement.allow_missing>` and :ref:`allow_missing_or_failed <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtRequirement.allow_missing_or_failed>` are implemented differently than other ``JwtRequirements``. Hence the usage of this field is different as follows if ``allow_missing`` or ``allow_missing_or_failed`` is used: * If a JWT has ``iss`` field, it needs to be specified by this field in one of ``JwtProviders``. * If a JWT doesn't have ``iss`` field, one of ``JwtProviders`` should fill this field empty. * Multiple ``JwtProviders`` should not have same value in this field. Examples: * https://securetoken.google.com * Example: 1234567-compute@developer.gserviceaccount.comstring issuer = 1;- Specified by:
getIssuerBytesin interfaceJwtProviderOrBuilder- Returns:
- The bytes for issuer.
-
setIssuer
Specify the `principal <https://tools.ietf.org/html/rfc7519#section-4.1.1>`_ that issued the JWT, usually a URL or an email address. It is optional. If specified, it has to match the ``iss`` field in JWT, otherwise the JWT ``iss`` field is not checked. .. note:: ``JwtRequirement`` :ref:`allow_missing <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtRequirement.allow_missing>` and :ref:`allow_missing_or_failed <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtRequirement.allow_missing_or_failed>` are implemented differently than other ``JwtRequirements``. Hence the usage of this field is different as follows if ``allow_missing`` or ``allow_missing_or_failed`` is used: * If a JWT has ``iss`` field, it needs to be specified by this field in one of ``JwtProviders``. * If a JWT doesn't have ``iss`` field, one of ``JwtProviders`` should fill this field empty. * Multiple ``JwtProviders`` should not have same value in this field. Examples: * https://securetoken.google.com * Example: 1234567-compute@developer.gserviceaccount.comstring issuer = 1;- Parameters:
value- The issuer to set.- Returns:
- This builder for chaining.
-
clearIssuer
Specify the `principal <https://tools.ietf.org/html/rfc7519#section-4.1.1>`_ that issued the JWT, usually a URL or an email address. It is optional. If specified, it has to match the ``iss`` field in JWT, otherwise the JWT ``iss`` field is not checked. .. note:: ``JwtRequirement`` :ref:`allow_missing <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtRequirement.allow_missing>` and :ref:`allow_missing_or_failed <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtRequirement.allow_missing_or_failed>` are implemented differently than other ``JwtRequirements``. Hence the usage of this field is different as follows if ``allow_missing`` or ``allow_missing_or_failed`` is used: * If a JWT has ``iss`` field, it needs to be specified by this field in one of ``JwtProviders``. * If a JWT doesn't have ``iss`` field, one of ``JwtProviders`` should fill this field empty. * Multiple ``JwtProviders`` should not have same value in this field. Examples: * https://securetoken.google.com * Example: 1234567-compute@developer.gserviceaccount.comstring issuer = 1;- Returns:
- This builder for chaining.
-
setIssuerBytes
Specify the `principal <https://tools.ietf.org/html/rfc7519#section-4.1.1>`_ that issued the JWT, usually a URL or an email address. It is optional. If specified, it has to match the ``iss`` field in JWT, otherwise the JWT ``iss`` field is not checked. .. note:: ``JwtRequirement`` :ref:`allow_missing <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtRequirement.allow_missing>` and :ref:`allow_missing_or_failed <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtRequirement.allow_missing_or_failed>` are implemented differently than other ``JwtRequirements``. Hence the usage of this field is different as follows if ``allow_missing`` or ``allow_missing_or_failed`` is used: * If a JWT has ``iss`` field, it needs to be specified by this field in one of ``JwtProviders``. * If a JWT doesn't have ``iss`` field, one of ``JwtProviders`` should fill this field empty. * Multiple ``JwtProviders`` should not have same value in this field. Examples: * https://securetoken.google.com * Example: 1234567-compute@developer.gserviceaccount.comstring issuer = 1;- Parameters:
value- The bytes for issuer to set.- Returns:
- This builder for chaining.
-
getAudiencesList
public com.google.protobuf.ProtocolStringList getAudiencesList()The list of JWT `audiences <https://tools.ietf.org/html/rfc7519#section-4.1.3>`_ are allowed to access. A JWT containing any of these audiences will be accepted. If not specified, will not check audiences in the token. Example: .. code-block:: yaml audiences: - bookstore_android.apps.googleusercontent.com - bookstore_web.apps.googleusercontent.comrepeated string audiences = 2;- Specified by:
getAudiencesListin interfaceJwtProviderOrBuilder- Returns:
- A list containing the audiences.
-
getAudiencesCount
public int getAudiencesCount()The list of JWT `audiences <https://tools.ietf.org/html/rfc7519#section-4.1.3>`_ are allowed to access. A JWT containing any of these audiences will be accepted. If not specified, will not check audiences in the token. Example: .. code-block:: yaml audiences: - bookstore_android.apps.googleusercontent.com - bookstore_web.apps.googleusercontent.comrepeated string audiences = 2;- Specified by:
getAudiencesCountin interfaceJwtProviderOrBuilder- Returns:
- The count of audiences.
-
getAudiences
The list of JWT `audiences <https://tools.ietf.org/html/rfc7519#section-4.1.3>`_ are allowed to access. A JWT containing any of these audiences will be accepted. If not specified, will not check audiences in the token. Example: .. code-block:: yaml audiences: - bookstore_android.apps.googleusercontent.com - bookstore_web.apps.googleusercontent.comrepeated string audiences = 2;- Specified by:
getAudiencesin interfaceJwtProviderOrBuilder- Parameters:
index- The index of the element to return.- Returns:
- The audiences at the given index.
-
getAudiencesBytes
public com.google.protobuf.ByteString getAudiencesBytes(int index) The list of JWT `audiences <https://tools.ietf.org/html/rfc7519#section-4.1.3>`_ are allowed to access. A JWT containing any of these audiences will be accepted. If not specified, will not check audiences in the token. Example: .. code-block:: yaml audiences: - bookstore_android.apps.googleusercontent.com - bookstore_web.apps.googleusercontent.comrepeated string audiences = 2;- Specified by:
getAudiencesBytesin interfaceJwtProviderOrBuilder- Parameters:
index- The index of the value to return.- Returns:
- The bytes of the audiences at the given index.
-
setAudiences
The list of JWT `audiences <https://tools.ietf.org/html/rfc7519#section-4.1.3>`_ are allowed to access. A JWT containing any of these audiences will be accepted. If not specified, will not check audiences in the token. Example: .. code-block:: yaml audiences: - bookstore_android.apps.googleusercontent.com - bookstore_web.apps.googleusercontent.comrepeated string audiences = 2;- Parameters:
index- The index to set the value at.value- The audiences to set.- Returns:
- This builder for chaining.
-
addAudiences
The list of JWT `audiences <https://tools.ietf.org/html/rfc7519#section-4.1.3>`_ are allowed to access. A JWT containing any of these audiences will be accepted. If not specified, will not check audiences in the token. Example: .. code-block:: yaml audiences: - bookstore_android.apps.googleusercontent.com - bookstore_web.apps.googleusercontent.comrepeated string audiences = 2;- Parameters:
value- The audiences to add.- Returns:
- This builder for chaining.
-
addAllAudiences
The list of JWT `audiences <https://tools.ietf.org/html/rfc7519#section-4.1.3>`_ are allowed to access. A JWT containing any of these audiences will be accepted. If not specified, will not check audiences in the token. Example: .. code-block:: yaml audiences: - bookstore_android.apps.googleusercontent.com - bookstore_web.apps.googleusercontent.comrepeated string audiences = 2;- Parameters:
values- The audiences to add.- Returns:
- This builder for chaining.
-
clearAudiences
The list of JWT `audiences <https://tools.ietf.org/html/rfc7519#section-4.1.3>`_ are allowed to access. A JWT containing any of these audiences will be accepted. If not specified, will not check audiences in the token. Example: .. code-block:: yaml audiences: - bookstore_android.apps.googleusercontent.com - bookstore_web.apps.googleusercontent.comrepeated string audiences = 2;- Returns:
- This builder for chaining.
-
addAudiencesBytes
The list of JWT `audiences <https://tools.ietf.org/html/rfc7519#section-4.1.3>`_ are allowed to access. A JWT containing any of these audiences will be accepted. If not specified, will not check audiences in the token. Example: .. code-block:: yaml audiences: - bookstore_android.apps.googleusercontent.com - bookstore_web.apps.googleusercontent.comrepeated string audiences = 2;- Parameters:
value- The bytes of the audiences to add.- Returns:
- This builder for chaining.
-
hasSubjects
public boolean hasSubjects()Restrict the `subjects <https://tools.ietf.org/html/rfc7519#section-4.1.2>`_ that the JwtProvider can assert. For instance, this could implement JWT-SVID `subject restrictions <https://github.com/spiffe/spiffe/blob/main/standards/JWT-SVID.md#31-subject>`_. If not specified, will not check subjects in the token. Example: .. code-block:: yaml subjects: prefix: spiffe://spiffe.example.com/.envoy.type.matcher.v3.StringMatcher subjects = 19;- Specified by:
hasSubjectsin interfaceJwtProviderOrBuilder- Returns:
- Whether the subjects field is set.
-
getSubjects
Restrict the `subjects <https://tools.ietf.org/html/rfc7519#section-4.1.2>`_ that the JwtProvider can assert. For instance, this could implement JWT-SVID `subject restrictions <https://github.com/spiffe/spiffe/blob/main/standards/JWT-SVID.md#31-subject>`_. If not specified, will not check subjects in the token. Example: .. code-block:: yaml subjects: prefix: spiffe://spiffe.example.com/.envoy.type.matcher.v3.StringMatcher subjects = 19;- Specified by:
getSubjectsin interfaceJwtProviderOrBuilder- Returns:
- The subjects.
-
setSubjects
Restrict the `subjects <https://tools.ietf.org/html/rfc7519#section-4.1.2>`_ that the JwtProvider can assert. For instance, this could implement JWT-SVID `subject restrictions <https://github.com/spiffe/spiffe/blob/main/standards/JWT-SVID.md#31-subject>`_. If not specified, will not check subjects in the token. Example: .. code-block:: yaml subjects: prefix: spiffe://spiffe.example.com/.envoy.type.matcher.v3.StringMatcher subjects = 19; -
setSubjects
Restrict the `subjects <https://tools.ietf.org/html/rfc7519#section-4.1.2>`_ that the JwtProvider can assert. For instance, this could implement JWT-SVID `subject restrictions <https://github.com/spiffe/spiffe/blob/main/standards/JWT-SVID.md#31-subject>`_. If not specified, will not check subjects in the token. Example: .. code-block:: yaml subjects: prefix: spiffe://spiffe.example.com/.envoy.type.matcher.v3.StringMatcher subjects = 19; -
mergeSubjects
Restrict the `subjects <https://tools.ietf.org/html/rfc7519#section-4.1.2>`_ that the JwtProvider can assert. For instance, this could implement JWT-SVID `subject restrictions <https://github.com/spiffe/spiffe/blob/main/standards/JWT-SVID.md#31-subject>`_. If not specified, will not check subjects in the token. Example: .. code-block:: yaml subjects: prefix: spiffe://spiffe.example.com/.envoy.type.matcher.v3.StringMatcher subjects = 19; -
clearSubjects
Restrict the `subjects <https://tools.ietf.org/html/rfc7519#section-4.1.2>`_ that the JwtProvider can assert. For instance, this could implement JWT-SVID `subject restrictions <https://github.com/spiffe/spiffe/blob/main/standards/JWT-SVID.md#31-subject>`_. If not specified, will not check subjects in the token. Example: .. code-block:: yaml subjects: prefix: spiffe://spiffe.example.com/.envoy.type.matcher.v3.StringMatcher subjects = 19; -
getSubjectsBuilder
Restrict the `subjects <https://tools.ietf.org/html/rfc7519#section-4.1.2>`_ that the JwtProvider can assert. For instance, this could implement JWT-SVID `subject restrictions <https://github.com/spiffe/spiffe/blob/main/standards/JWT-SVID.md#31-subject>`_. If not specified, will not check subjects in the token. Example: .. code-block:: yaml subjects: prefix: spiffe://spiffe.example.com/.envoy.type.matcher.v3.StringMatcher subjects = 19; -
getSubjectsOrBuilder
Restrict the `subjects <https://tools.ietf.org/html/rfc7519#section-4.1.2>`_ that the JwtProvider can assert. For instance, this could implement JWT-SVID `subject restrictions <https://github.com/spiffe/spiffe/blob/main/standards/JWT-SVID.md#31-subject>`_. If not specified, will not check subjects in the token. Example: .. code-block:: yaml subjects: prefix: spiffe://spiffe.example.com/.envoy.type.matcher.v3.StringMatcher subjects = 19;- Specified by:
getSubjectsOrBuilderin interfaceJwtProviderOrBuilder
-
getRequireExpiration
public boolean getRequireExpiration()Requires that the credential contains an `expiration <https://tools.ietf.org/html/rfc7519#section-4.1.4>`_. For instance, this could implement JWT-SVID `expiration restrictions <https://github.com/spiffe/spiffe/blob/main/standards/JWT-SVID.md#33-expiration-time>`_. Unlike ``max_lifetime``, this only requires that expiration is present, where ``max_lifetime`` also checks the value. Example: .. code-block:: yaml require_expiration: truebool require_expiration = 20;- Specified by:
getRequireExpirationin interfaceJwtProviderOrBuilder- Returns:
- The requireExpiration.
-
setRequireExpiration
Requires that the credential contains an `expiration <https://tools.ietf.org/html/rfc7519#section-4.1.4>`_. For instance, this could implement JWT-SVID `expiration restrictions <https://github.com/spiffe/spiffe/blob/main/standards/JWT-SVID.md#33-expiration-time>`_. Unlike ``max_lifetime``, this only requires that expiration is present, where ``max_lifetime`` also checks the value. Example: .. code-block:: yaml require_expiration: truebool require_expiration = 20;- Parameters:
value- The requireExpiration to set.- Returns:
- This builder for chaining.
-
clearRequireExpiration
Requires that the credential contains an `expiration <https://tools.ietf.org/html/rfc7519#section-4.1.4>`_. For instance, this could implement JWT-SVID `expiration restrictions <https://github.com/spiffe/spiffe/blob/main/standards/JWT-SVID.md#33-expiration-time>`_. Unlike ``max_lifetime``, this only requires that expiration is present, where ``max_lifetime`` also checks the value. Example: .. code-block:: yaml require_expiration: truebool require_expiration = 20;- Returns:
- This builder for chaining.
-
hasMaxLifetime
public boolean hasMaxLifetime()Restrict the maximum remaining lifetime of a credential from the JwtProvider. Credential lifetime is the difference between the current time and the expiration of the credential. For instance, the following example will reject credentials that have a lifetime longer than 24 hours. If not set, expiration checking still occurs, but there is no limit on credential lifetime. If set, takes precedence over ``require_expiration``. Example: .. code-block:: yaml max_lifetime: seconds: 86400.google.protobuf.Duration max_lifetime = 21;- Specified by:
hasMaxLifetimein interfaceJwtProviderOrBuilder- Returns:
- Whether the maxLifetime field is set.
-
getMaxLifetime
public com.google.protobuf.Duration getMaxLifetime()Restrict the maximum remaining lifetime of a credential from the JwtProvider. Credential lifetime is the difference between the current time and the expiration of the credential. For instance, the following example will reject credentials that have a lifetime longer than 24 hours. If not set, expiration checking still occurs, but there is no limit on credential lifetime. If set, takes precedence over ``require_expiration``. Example: .. code-block:: yaml max_lifetime: seconds: 86400.google.protobuf.Duration max_lifetime = 21;- Specified by:
getMaxLifetimein interfaceJwtProviderOrBuilder- Returns:
- The maxLifetime.
-
setMaxLifetime
Restrict the maximum remaining lifetime of a credential from the JwtProvider. Credential lifetime is the difference between the current time and the expiration of the credential. For instance, the following example will reject credentials that have a lifetime longer than 24 hours. If not set, expiration checking still occurs, but there is no limit on credential lifetime. If set, takes precedence over ``require_expiration``. Example: .. code-block:: yaml max_lifetime: seconds: 86400.google.protobuf.Duration max_lifetime = 21; -
setMaxLifetime
Restrict the maximum remaining lifetime of a credential from the JwtProvider. Credential lifetime is the difference between the current time and the expiration of the credential. For instance, the following example will reject credentials that have a lifetime longer than 24 hours. If not set, expiration checking still occurs, but there is no limit on credential lifetime. If set, takes precedence over ``require_expiration``. Example: .. code-block:: yaml max_lifetime: seconds: 86400.google.protobuf.Duration max_lifetime = 21; -
mergeMaxLifetime
Restrict the maximum remaining lifetime of a credential from the JwtProvider. Credential lifetime is the difference between the current time and the expiration of the credential. For instance, the following example will reject credentials that have a lifetime longer than 24 hours. If not set, expiration checking still occurs, but there is no limit on credential lifetime. If set, takes precedence over ``require_expiration``. Example: .. code-block:: yaml max_lifetime: seconds: 86400.google.protobuf.Duration max_lifetime = 21; -
clearMaxLifetime
Restrict the maximum remaining lifetime of a credential from the JwtProvider. Credential lifetime is the difference between the current time and the expiration of the credential. For instance, the following example will reject credentials that have a lifetime longer than 24 hours. If not set, expiration checking still occurs, but there is no limit on credential lifetime. If set, takes precedence over ``require_expiration``. Example: .. code-block:: yaml max_lifetime: seconds: 86400.google.protobuf.Duration max_lifetime = 21; -
getMaxLifetimeBuilder
public com.google.protobuf.Duration.Builder getMaxLifetimeBuilder()Restrict the maximum remaining lifetime of a credential from the JwtProvider. Credential lifetime is the difference between the current time and the expiration of the credential. For instance, the following example will reject credentials that have a lifetime longer than 24 hours. If not set, expiration checking still occurs, but there is no limit on credential lifetime. If set, takes precedence over ``require_expiration``. Example: .. code-block:: yaml max_lifetime: seconds: 86400.google.protobuf.Duration max_lifetime = 21; -
getMaxLifetimeOrBuilder
public com.google.protobuf.DurationOrBuilder getMaxLifetimeOrBuilder()Restrict the maximum remaining lifetime of a credential from the JwtProvider. Credential lifetime is the difference between the current time and the expiration of the credential. For instance, the following example will reject credentials that have a lifetime longer than 24 hours. If not set, expiration checking still occurs, but there is no limit on credential lifetime. If set, takes precedence over ``require_expiration``. Example: .. code-block:: yaml max_lifetime: seconds: 86400.google.protobuf.Duration max_lifetime = 21;- Specified by:
getMaxLifetimeOrBuilderin interfaceJwtProviderOrBuilder
-
hasRemoteJwks
public boolean hasRemoteJwks()JWKS can be fetched from remote server via HTTP/HTTPS. This field specifies the remote HTTP URI and how the fetched JWKS should be cached. Example: .. code-block:: yaml remote_jwks: http_uri: uri: https://www.googleapis.com/oauth2/v1/certs cluster: jwt.www.googleapis.com|443 timeout: 1s cache_duration: seconds: 300.envoy.extensions.filters.http.jwt_authn.v3.RemoteJwks remote_jwks = 3;- Specified by:
hasRemoteJwksin interfaceJwtProviderOrBuilder- Returns:
- Whether the remoteJwks field is set.
-
getRemoteJwks
JWKS can be fetched from remote server via HTTP/HTTPS. This field specifies the remote HTTP URI and how the fetched JWKS should be cached. Example: .. code-block:: yaml remote_jwks: http_uri: uri: https://www.googleapis.com/oauth2/v1/certs cluster: jwt.www.googleapis.com|443 timeout: 1s cache_duration: seconds: 300.envoy.extensions.filters.http.jwt_authn.v3.RemoteJwks remote_jwks = 3;- Specified by:
getRemoteJwksin interfaceJwtProviderOrBuilder- Returns:
- The remoteJwks.
-
setRemoteJwks
JWKS can be fetched from remote server via HTTP/HTTPS. This field specifies the remote HTTP URI and how the fetched JWKS should be cached. Example: .. code-block:: yaml remote_jwks: http_uri: uri: https://www.googleapis.com/oauth2/v1/certs cluster: jwt.www.googleapis.com|443 timeout: 1s cache_duration: seconds: 300.envoy.extensions.filters.http.jwt_authn.v3.RemoteJwks remote_jwks = 3; -
setRemoteJwks
JWKS can be fetched from remote server via HTTP/HTTPS. This field specifies the remote HTTP URI and how the fetched JWKS should be cached. Example: .. code-block:: yaml remote_jwks: http_uri: uri: https://www.googleapis.com/oauth2/v1/certs cluster: jwt.www.googleapis.com|443 timeout: 1s cache_duration: seconds: 300.envoy.extensions.filters.http.jwt_authn.v3.RemoteJwks remote_jwks = 3; -
mergeRemoteJwks
JWKS can be fetched from remote server via HTTP/HTTPS. This field specifies the remote HTTP URI and how the fetched JWKS should be cached. Example: .. code-block:: yaml remote_jwks: http_uri: uri: https://www.googleapis.com/oauth2/v1/certs cluster: jwt.www.googleapis.com|443 timeout: 1s cache_duration: seconds: 300.envoy.extensions.filters.http.jwt_authn.v3.RemoteJwks remote_jwks = 3; -
clearRemoteJwks
JWKS can be fetched from remote server via HTTP/HTTPS. This field specifies the remote HTTP URI and how the fetched JWKS should be cached. Example: .. code-block:: yaml remote_jwks: http_uri: uri: https://www.googleapis.com/oauth2/v1/certs cluster: jwt.www.googleapis.com|443 timeout: 1s cache_duration: seconds: 300.envoy.extensions.filters.http.jwt_authn.v3.RemoteJwks remote_jwks = 3; -
getRemoteJwksBuilder
JWKS can be fetched from remote server via HTTP/HTTPS. This field specifies the remote HTTP URI and how the fetched JWKS should be cached. Example: .. code-block:: yaml remote_jwks: http_uri: uri: https://www.googleapis.com/oauth2/v1/certs cluster: jwt.www.googleapis.com|443 timeout: 1s cache_duration: seconds: 300.envoy.extensions.filters.http.jwt_authn.v3.RemoteJwks remote_jwks = 3; -
getRemoteJwksOrBuilder
JWKS can be fetched from remote server via HTTP/HTTPS. This field specifies the remote HTTP URI and how the fetched JWKS should be cached. Example: .. code-block:: yaml remote_jwks: http_uri: uri: https://www.googleapis.com/oauth2/v1/certs cluster: jwt.www.googleapis.com|443 timeout: 1s cache_duration: seconds: 300.envoy.extensions.filters.http.jwt_authn.v3.RemoteJwks remote_jwks = 3;- Specified by:
getRemoteJwksOrBuilderin interfaceJwtProviderOrBuilder
-
hasLocalJwks
public boolean hasLocalJwks()JWKS is in local data source. It could be either in a local file or embedded in the inline_string. Example: local file .. code-block:: yaml local_jwks: filename: /etc/envoy/jwks/jwks1.txt Example: inline_string .. code-block:: yaml local_jwks: inline_string: ACADADADADA.envoy.config.core.v3.DataSource local_jwks = 4;- Specified by:
hasLocalJwksin interfaceJwtProviderOrBuilder- Returns:
- Whether the localJwks field is set.
-
getLocalJwks
JWKS is in local data source. It could be either in a local file or embedded in the inline_string. Example: local file .. code-block:: yaml local_jwks: filename: /etc/envoy/jwks/jwks1.txt Example: inline_string .. code-block:: yaml local_jwks: inline_string: ACADADADADA.envoy.config.core.v3.DataSource local_jwks = 4;- Specified by:
getLocalJwksin interfaceJwtProviderOrBuilder- Returns:
- The localJwks.
-
setLocalJwks
JWKS is in local data source. It could be either in a local file or embedded in the inline_string. Example: local file .. code-block:: yaml local_jwks: filename: /etc/envoy/jwks/jwks1.txt Example: inline_string .. code-block:: yaml local_jwks: inline_string: ACADADADADA.envoy.config.core.v3.DataSource local_jwks = 4; -
setLocalJwks
JWKS is in local data source. It could be either in a local file or embedded in the inline_string. Example: local file .. code-block:: yaml local_jwks: filename: /etc/envoy/jwks/jwks1.txt Example: inline_string .. code-block:: yaml local_jwks: inline_string: ACADADADADA.envoy.config.core.v3.DataSource local_jwks = 4; -
mergeLocalJwks
JWKS is in local data source. It could be either in a local file or embedded in the inline_string. Example: local file .. code-block:: yaml local_jwks: filename: /etc/envoy/jwks/jwks1.txt Example: inline_string .. code-block:: yaml local_jwks: inline_string: ACADADADADA.envoy.config.core.v3.DataSource local_jwks = 4; -
clearLocalJwks
JWKS is in local data source. It could be either in a local file or embedded in the inline_string. Example: local file .. code-block:: yaml local_jwks: filename: /etc/envoy/jwks/jwks1.txt Example: inline_string .. code-block:: yaml local_jwks: inline_string: ACADADADADA.envoy.config.core.v3.DataSource local_jwks = 4; -
getLocalJwksBuilder
JWKS is in local data source. It could be either in a local file or embedded in the inline_string. Example: local file .. code-block:: yaml local_jwks: filename: /etc/envoy/jwks/jwks1.txt Example: inline_string .. code-block:: yaml local_jwks: inline_string: ACADADADADA.envoy.config.core.v3.DataSource local_jwks = 4; -
getLocalJwksOrBuilder
JWKS is in local data source. It could be either in a local file or embedded in the inline_string. Example: local file .. code-block:: yaml local_jwks: filename: /etc/envoy/jwks/jwks1.txt Example: inline_string .. code-block:: yaml local_jwks: inline_string: ACADADADADA.envoy.config.core.v3.DataSource local_jwks = 4;- Specified by:
getLocalJwksOrBuilderin interfaceJwtProviderOrBuilder
-
getForward
public boolean getForward()If false, the JWT is removed in the request after a success verification. If true, the JWT is not removed in the request. Default value is false. caveat: only works for from_header/from_params & has no effect for JWTs extracted through from_cookies.
bool forward = 5;- Specified by:
getForwardin interfaceJwtProviderOrBuilder- Returns:
- The forward.
-
setForward
If false, the JWT is removed in the request after a success verification. If true, the JWT is not removed in the request. Default value is false. caveat: only works for from_header/from_params & has no effect for JWTs extracted through from_cookies.
bool forward = 5;- Parameters:
value- The forward to set.- Returns:
- This builder for chaining.
-
clearForward
If false, the JWT is removed in the request after a success verification. If true, the JWT is not removed in the request. Default value is false. caveat: only works for from_header/from_params & has no effect for JWTs extracted through from_cookies.
bool forward = 5;- Returns:
- This builder for chaining.
-
getFromHeadersList
Two fields below define where to extract the JWT from an HTTP request. If no explicit location is specified, the following default locations are tried in order: 1. The Authorization header using the `Bearer schema <https://tools.ietf.org/html/rfc6750#section-2.1>`_. Example:: Authorization: Bearer <token>. 2. `access_token <https://tools.ietf.org/html/rfc6750#section-2.3>`_ query parameter. Multiple JWTs can be verified for a request. Each JWT has to be extracted from the locations its provider specified or from the default locations. Specify the HTTP headers to extract the JWT. For examples, following config: .. code-block:: yaml from_headers: - name: x-goog-iap-jwt-assertion can be used to extract token from header:: ``x-goog-iap-jwt-assertion: <JWT>``.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtHeader from_headers = 6;- Specified by:
getFromHeadersListin interfaceJwtProviderOrBuilder
-
getFromHeadersCount
public int getFromHeadersCount()Two fields below define where to extract the JWT from an HTTP request. If no explicit location is specified, the following default locations are tried in order: 1. The Authorization header using the `Bearer schema <https://tools.ietf.org/html/rfc6750#section-2.1>`_. Example:: Authorization: Bearer <token>. 2. `access_token <https://tools.ietf.org/html/rfc6750#section-2.3>`_ query parameter. Multiple JWTs can be verified for a request. Each JWT has to be extracted from the locations its provider specified or from the default locations. Specify the HTTP headers to extract the JWT. For examples, following config: .. code-block:: yaml from_headers: - name: x-goog-iap-jwt-assertion can be used to extract token from header:: ``x-goog-iap-jwt-assertion: <JWT>``.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtHeader from_headers = 6;- Specified by:
getFromHeadersCountin interfaceJwtProviderOrBuilder
-
getFromHeaders
Two fields below define where to extract the JWT from an HTTP request. If no explicit location is specified, the following default locations are tried in order: 1. The Authorization header using the `Bearer schema <https://tools.ietf.org/html/rfc6750#section-2.1>`_. Example:: Authorization: Bearer <token>. 2. `access_token <https://tools.ietf.org/html/rfc6750#section-2.3>`_ query parameter. Multiple JWTs can be verified for a request. Each JWT has to be extracted from the locations its provider specified or from the default locations. Specify the HTTP headers to extract the JWT. For examples, following config: .. code-block:: yaml from_headers: - name: x-goog-iap-jwt-assertion can be used to extract token from header:: ``x-goog-iap-jwt-assertion: <JWT>``.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtHeader from_headers = 6;- Specified by:
getFromHeadersin interfaceJwtProviderOrBuilder
-
setFromHeaders
Two fields below define where to extract the JWT from an HTTP request. If no explicit location is specified, the following default locations are tried in order: 1. The Authorization header using the `Bearer schema <https://tools.ietf.org/html/rfc6750#section-2.1>`_. Example:: Authorization: Bearer <token>. 2. `access_token <https://tools.ietf.org/html/rfc6750#section-2.3>`_ query parameter. Multiple JWTs can be verified for a request. Each JWT has to be extracted from the locations its provider specified or from the default locations. Specify the HTTP headers to extract the JWT. For examples, following config: .. code-block:: yaml from_headers: - name: x-goog-iap-jwt-assertion can be used to extract token from header:: ``x-goog-iap-jwt-assertion: <JWT>``.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtHeader from_headers = 6; -
setFromHeaders
Two fields below define where to extract the JWT from an HTTP request. If no explicit location is specified, the following default locations are tried in order: 1. The Authorization header using the `Bearer schema <https://tools.ietf.org/html/rfc6750#section-2.1>`_. Example:: Authorization: Bearer <token>. 2. `access_token <https://tools.ietf.org/html/rfc6750#section-2.3>`_ query parameter. Multiple JWTs can be verified for a request. Each JWT has to be extracted from the locations its provider specified or from the default locations. Specify the HTTP headers to extract the JWT. For examples, following config: .. code-block:: yaml from_headers: - name: x-goog-iap-jwt-assertion can be used to extract token from header:: ``x-goog-iap-jwt-assertion: <JWT>``.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtHeader from_headers = 6; -
addFromHeaders
Two fields below define where to extract the JWT from an HTTP request. If no explicit location is specified, the following default locations are tried in order: 1. The Authorization header using the `Bearer schema <https://tools.ietf.org/html/rfc6750#section-2.1>`_. Example:: Authorization: Bearer <token>. 2. `access_token <https://tools.ietf.org/html/rfc6750#section-2.3>`_ query parameter. Multiple JWTs can be verified for a request. Each JWT has to be extracted from the locations its provider specified or from the default locations. Specify the HTTP headers to extract the JWT. For examples, following config: .. code-block:: yaml from_headers: - name: x-goog-iap-jwt-assertion can be used to extract token from header:: ``x-goog-iap-jwt-assertion: <JWT>``.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtHeader from_headers = 6; -
addFromHeaders
Two fields below define where to extract the JWT from an HTTP request. If no explicit location is specified, the following default locations are tried in order: 1. The Authorization header using the `Bearer schema <https://tools.ietf.org/html/rfc6750#section-2.1>`_. Example:: Authorization: Bearer <token>. 2. `access_token <https://tools.ietf.org/html/rfc6750#section-2.3>`_ query parameter. Multiple JWTs can be verified for a request. Each JWT has to be extracted from the locations its provider specified or from the default locations. Specify the HTTP headers to extract the JWT. For examples, following config: .. code-block:: yaml from_headers: - name: x-goog-iap-jwt-assertion can be used to extract token from header:: ``x-goog-iap-jwt-assertion: <JWT>``.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtHeader from_headers = 6; -
addFromHeaders
Two fields below define where to extract the JWT from an HTTP request. If no explicit location is specified, the following default locations are tried in order: 1. The Authorization header using the `Bearer schema <https://tools.ietf.org/html/rfc6750#section-2.1>`_. Example:: Authorization: Bearer <token>. 2. `access_token <https://tools.ietf.org/html/rfc6750#section-2.3>`_ query parameter. Multiple JWTs can be verified for a request. Each JWT has to be extracted from the locations its provider specified or from the default locations. Specify the HTTP headers to extract the JWT. For examples, following config: .. code-block:: yaml from_headers: - name: x-goog-iap-jwt-assertion can be used to extract token from header:: ``x-goog-iap-jwt-assertion: <JWT>``.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtHeader from_headers = 6; -
addFromHeaders
Two fields below define where to extract the JWT from an HTTP request. If no explicit location is specified, the following default locations are tried in order: 1. The Authorization header using the `Bearer schema <https://tools.ietf.org/html/rfc6750#section-2.1>`_. Example:: Authorization: Bearer <token>. 2. `access_token <https://tools.ietf.org/html/rfc6750#section-2.3>`_ query parameter. Multiple JWTs can be verified for a request. Each JWT has to be extracted from the locations its provider specified or from the default locations. Specify the HTTP headers to extract the JWT. For examples, following config: .. code-block:: yaml from_headers: - name: x-goog-iap-jwt-assertion can be used to extract token from header:: ``x-goog-iap-jwt-assertion: <JWT>``.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtHeader from_headers = 6; -
addAllFromHeaders
Two fields below define where to extract the JWT from an HTTP request. If no explicit location is specified, the following default locations are tried in order: 1. The Authorization header using the `Bearer schema <https://tools.ietf.org/html/rfc6750#section-2.1>`_. Example:: Authorization: Bearer <token>. 2. `access_token <https://tools.ietf.org/html/rfc6750#section-2.3>`_ query parameter. Multiple JWTs can be verified for a request. Each JWT has to be extracted from the locations its provider specified or from the default locations. Specify the HTTP headers to extract the JWT. For examples, following config: .. code-block:: yaml from_headers: - name: x-goog-iap-jwt-assertion can be used to extract token from header:: ``x-goog-iap-jwt-assertion: <JWT>``.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtHeader from_headers = 6; -
clearFromHeaders
Two fields below define where to extract the JWT from an HTTP request. If no explicit location is specified, the following default locations are tried in order: 1. The Authorization header using the `Bearer schema <https://tools.ietf.org/html/rfc6750#section-2.1>`_. Example:: Authorization: Bearer <token>. 2. `access_token <https://tools.ietf.org/html/rfc6750#section-2.3>`_ query parameter. Multiple JWTs can be verified for a request. Each JWT has to be extracted from the locations its provider specified or from the default locations. Specify the HTTP headers to extract the JWT. For examples, following config: .. code-block:: yaml from_headers: - name: x-goog-iap-jwt-assertion can be used to extract token from header:: ``x-goog-iap-jwt-assertion: <JWT>``.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtHeader from_headers = 6; -
removeFromHeaders
Two fields below define where to extract the JWT from an HTTP request. If no explicit location is specified, the following default locations are tried in order: 1. The Authorization header using the `Bearer schema <https://tools.ietf.org/html/rfc6750#section-2.1>`_. Example:: Authorization: Bearer <token>. 2. `access_token <https://tools.ietf.org/html/rfc6750#section-2.3>`_ query parameter. Multiple JWTs can be verified for a request. Each JWT has to be extracted from the locations its provider specified or from the default locations. Specify the HTTP headers to extract the JWT. For examples, following config: .. code-block:: yaml from_headers: - name: x-goog-iap-jwt-assertion can be used to extract token from header:: ``x-goog-iap-jwt-assertion: <JWT>``.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtHeader from_headers = 6; -
getFromHeadersBuilder
Two fields below define where to extract the JWT from an HTTP request. If no explicit location is specified, the following default locations are tried in order: 1. The Authorization header using the `Bearer schema <https://tools.ietf.org/html/rfc6750#section-2.1>`_. Example:: Authorization: Bearer <token>. 2. `access_token <https://tools.ietf.org/html/rfc6750#section-2.3>`_ query parameter. Multiple JWTs can be verified for a request. Each JWT has to be extracted from the locations its provider specified or from the default locations. Specify the HTTP headers to extract the JWT. For examples, following config: .. code-block:: yaml from_headers: - name: x-goog-iap-jwt-assertion can be used to extract token from header:: ``x-goog-iap-jwt-assertion: <JWT>``.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtHeader from_headers = 6; -
getFromHeadersOrBuilder
Two fields below define where to extract the JWT from an HTTP request. If no explicit location is specified, the following default locations are tried in order: 1. The Authorization header using the `Bearer schema <https://tools.ietf.org/html/rfc6750#section-2.1>`_. Example:: Authorization: Bearer <token>. 2. `access_token <https://tools.ietf.org/html/rfc6750#section-2.3>`_ query parameter. Multiple JWTs can be verified for a request. Each JWT has to be extracted from the locations its provider specified or from the default locations. Specify the HTTP headers to extract the JWT. For examples, following config: .. code-block:: yaml from_headers: - name: x-goog-iap-jwt-assertion can be used to extract token from header:: ``x-goog-iap-jwt-assertion: <JWT>``.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtHeader from_headers = 6;- Specified by:
getFromHeadersOrBuilderin interfaceJwtProviderOrBuilder
-
getFromHeadersOrBuilderList
Two fields below define where to extract the JWT from an HTTP request. If no explicit location is specified, the following default locations are tried in order: 1. The Authorization header using the `Bearer schema <https://tools.ietf.org/html/rfc6750#section-2.1>`_. Example:: Authorization: Bearer <token>. 2. `access_token <https://tools.ietf.org/html/rfc6750#section-2.3>`_ query parameter. Multiple JWTs can be verified for a request. Each JWT has to be extracted from the locations its provider specified or from the default locations. Specify the HTTP headers to extract the JWT. For examples, following config: .. code-block:: yaml from_headers: - name: x-goog-iap-jwt-assertion can be used to extract token from header:: ``x-goog-iap-jwt-assertion: <JWT>``.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtHeader from_headers = 6;- Specified by:
getFromHeadersOrBuilderListin interfaceJwtProviderOrBuilder
-
addFromHeadersBuilder
Two fields below define where to extract the JWT from an HTTP request. If no explicit location is specified, the following default locations are tried in order: 1. The Authorization header using the `Bearer schema <https://tools.ietf.org/html/rfc6750#section-2.1>`_. Example:: Authorization: Bearer <token>. 2. `access_token <https://tools.ietf.org/html/rfc6750#section-2.3>`_ query parameter. Multiple JWTs can be verified for a request. Each JWT has to be extracted from the locations its provider specified or from the default locations. Specify the HTTP headers to extract the JWT. For examples, following config: .. code-block:: yaml from_headers: - name: x-goog-iap-jwt-assertion can be used to extract token from header:: ``x-goog-iap-jwt-assertion: <JWT>``.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtHeader from_headers = 6; -
addFromHeadersBuilder
Two fields below define where to extract the JWT from an HTTP request. If no explicit location is specified, the following default locations are tried in order: 1. The Authorization header using the `Bearer schema <https://tools.ietf.org/html/rfc6750#section-2.1>`_. Example:: Authorization: Bearer <token>. 2. `access_token <https://tools.ietf.org/html/rfc6750#section-2.3>`_ query parameter. Multiple JWTs can be verified for a request. Each JWT has to be extracted from the locations its provider specified or from the default locations. Specify the HTTP headers to extract the JWT. For examples, following config: .. code-block:: yaml from_headers: - name: x-goog-iap-jwt-assertion can be used to extract token from header:: ``x-goog-iap-jwt-assertion: <JWT>``.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtHeader from_headers = 6; -
getFromHeadersBuilderList
Two fields below define where to extract the JWT from an HTTP request. If no explicit location is specified, the following default locations are tried in order: 1. The Authorization header using the `Bearer schema <https://tools.ietf.org/html/rfc6750#section-2.1>`_. Example:: Authorization: Bearer <token>. 2. `access_token <https://tools.ietf.org/html/rfc6750#section-2.3>`_ query parameter. Multiple JWTs can be verified for a request. Each JWT has to be extracted from the locations its provider specified or from the default locations. Specify the HTTP headers to extract the JWT. For examples, following config: .. code-block:: yaml from_headers: - name: x-goog-iap-jwt-assertion can be used to extract token from header:: ``x-goog-iap-jwt-assertion: <JWT>``.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtHeader from_headers = 6; -
getFromParamsList
public com.google.protobuf.ProtocolStringList getFromParamsList()JWT is sent in a query parameter. ``jwt_params`` represents the query parameter names. For example, if config is: .. code-block:: yaml from_params: - jwt_token The JWT format in query parameter is:: /path?jwt_token=<JWT>repeated string from_params = 7;- Specified by:
getFromParamsListin interfaceJwtProviderOrBuilder- Returns:
- A list containing the fromParams.
-
getFromParamsCount
public int getFromParamsCount()JWT is sent in a query parameter. ``jwt_params`` represents the query parameter names. For example, if config is: .. code-block:: yaml from_params: - jwt_token The JWT format in query parameter is:: /path?jwt_token=<JWT>repeated string from_params = 7;- Specified by:
getFromParamsCountin interfaceJwtProviderOrBuilder- Returns:
- The count of fromParams.
-
getFromParams
JWT is sent in a query parameter. ``jwt_params`` represents the query parameter names. For example, if config is: .. code-block:: yaml from_params: - jwt_token The JWT format in query parameter is:: /path?jwt_token=<JWT>repeated string from_params = 7;- Specified by:
getFromParamsin interfaceJwtProviderOrBuilder- Parameters:
index- The index of the element to return.- Returns:
- The fromParams at the given index.
-
getFromParamsBytes
public com.google.protobuf.ByteString getFromParamsBytes(int index) JWT is sent in a query parameter. ``jwt_params`` represents the query parameter names. For example, if config is: .. code-block:: yaml from_params: - jwt_token The JWT format in query parameter is:: /path?jwt_token=<JWT>repeated string from_params = 7;- Specified by:
getFromParamsBytesin interfaceJwtProviderOrBuilder- Parameters:
index- The index of the value to return.- Returns:
- The bytes of the fromParams at the given index.
-
setFromParams
JWT is sent in a query parameter. ``jwt_params`` represents the query parameter names. For example, if config is: .. code-block:: yaml from_params: - jwt_token The JWT format in query parameter is:: /path?jwt_token=<JWT>repeated string from_params = 7;- Parameters:
index- The index to set the value at.value- The fromParams to set.- Returns:
- This builder for chaining.
-
addFromParams
JWT is sent in a query parameter. ``jwt_params`` represents the query parameter names. For example, if config is: .. code-block:: yaml from_params: - jwt_token The JWT format in query parameter is:: /path?jwt_token=<JWT>repeated string from_params = 7;- Parameters:
value- The fromParams to add.- Returns:
- This builder for chaining.
-
addAllFromParams
JWT is sent in a query parameter. ``jwt_params`` represents the query parameter names. For example, if config is: .. code-block:: yaml from_params: - jwt_token The JWT format in query parameter is:: /path?jwt_token=<JWT>repeated string from_params = 7;- Parameters:
values- The fromParams to add.- Returns:
- This builder for chaining.
-
clearFromParams
JWT is sent in a query parameter. ``jwt_params`` represents the query parameter names. For example, if config is: .. code-block:: yaml from_params: - jwt_token The JWT format in query parameter is:: /path?jwt_token=<JWT>repeated string from_params = 7;- Returns:
- This builder for chaining.
-
addFromParamsBytes
JWT is sent in a query parameter. ``jwt_params`` represents the query parameter names. For example, if config is: .. code-block:: yaml from_params: - jwt_token The JWT format in query parameter is:: /path?jwt_token=<JWT>repeated string from_params = 7;- Parameters:
value- The bytes of the fromParams to add.- Returns:
- This builder for chaining.
-
getFromCookiesList
public com.google.protobuf.ProtocolStringList getFromCookiesList()JWT is sent in a cookie. ``from_cookies`` represents the cookie names to extract from. For example, if config is: .. code-block:: yaml from_cookies: - auth-token Then JWT will be extracted from ``auth-token`` cookie in the request.
repeated string from_cookies = 13;- Specified by:
getFromCookiesListin interfaceJwtProviderOrBuilder- Returns:
- A list containing the fromCookies.
-
getFromCookiesCount
public int getFromCookiesCount()JWT is sent in a cookie. ``from_cookies`` represents the cookie names to extract from. For example, if config is: .. code-block:: yaml from_cookies: - auth-token Then JWT will be extracted from ``auth-token`` cookie in the request.
repeated string from_cookies = 13;- Specified by:
getFromCookiesCountin interfaceJwtProviderOrBuilder- Returns:
- The count of fromCookies.
-
getFromCookies
JWT is sent in a cookie. ``from_cookies`` represents the cookie names to extract from. For example, if config is: .. code-block:: yaml from_cookies: - auth-token Then JWT will be extracted from ``auth-token`` cookie in the request.
repeated string from_cookies = 13;- Specified by:
getFromCookiesin interfaceJwtProviderOrBuilder- Parameters:
index- The index of the element to return.- Returns:
- The fromCookies at the given index.
-
getFromCookiesBytes
public com.google.protobuf.ByteString getFromCookiesBytes(int index) JWT is sent in a cookie. ``from_cookies`` represents the cookie names to extract from. For example, if config is: .. code-block:: yaml from_cookies: - auth-token Then JWT will be extracted from ``auth-token`` cookie in the request.
repeated string from_cookies = 13;- Specified by:
getFromCookiesBytesin interfaceJwtProviderOrBuilder- Parameters:
index- The index of the value to return.- Returns:
- The bytes of the fromCookies at the given index.
-
setFromCookies
JWT is sent in a cookie. ``from_cookies`` represents the cookie names to extract from. For example, if config is: .. code-block:: yaml from_cookies: - auth-token Then JWT will be extracted from ``auth-token`` cookie in the request.
repeated string from_cookies = 13;- Parameters:
index- The index to set the value at.value- The fromCookies to set.- Returns:
- This builder for chaining.
-
addFromCookies
JWT is sent in a cookie. ``from_cookies`` represents the cookie names to extract from. For example, if config is: .. code-block:: yaml from_cookies: - auth-token Then JWT will be extracted from ``auth-token`` cookie in the request.
repeated string from_cookies = 13;- Parameters:
value- The fromCookies to add.- Returns:
- This builder for chaining.
-
addAllFromCookies
JWT is sent in a cookie. ``from_cookies`` represents the cookie names to extract from. For example, if config is: .. code-block:: yaml from_cookies: - auth-token Then JWT will be extracted from ``auth-token`` cookie in the request.
repeated string from_cookies = 13;- Parameters:
values- The fromCookies to add.- Returns:
- This builder for chaining.
-
clearFromCookies
JWT is sent in a cookie. ``from_cookies`` represents the cookie names to extract from. For example, if config is: .. code-block:: yaml from_cookies: - auth-token Then JWT will be extracted from ``auth-token`` cookie in the request.
repeated string from_cookies = 13;- Returns:
- This builder for chaining.
-
addFromCookiesBytes
JWT is sent in a cookie. ``from_cookies`` represents the cookie names to extract from. For example, if config is: .. code-block:: yaml from_cookies: - auth-token Then JWT will be extracted from ``auth-token`` cookie in the request.
repeated string from_cookies = 13;- Parameters:
value- The bytes of the fromCookies to add.- Returns:
- This builder for chaining.
-
getForwardPayloadHeader
This field specifies the header name to forward a successfully verified JWT payload to the backend. The forwarded data is:: base64url_encoded(jwt_payload_in_JSON) If it is not specified, the payload will not be forwarded.string forward_payload_header = 8 [(.validate.rules) = { ... }- Specified by:
getForwardPayloadHeaderin interfaceJwtProviderOrBuilder- Returns:
- The forwardPayloadHeader.
-
getForwardPayloadHeaderBytes
public com.google.protobuf.ByteString getForwardPayloadHeaderBytes()This field specifies the header name to forward a successfully verified JWT payload to the backend. The forwarded data is:: base64url_encoded(jwt_payload_in_JSON) If it is not specified, the payload will not be forwarded.string forward_payload_header = 8 [(.validate.rules) = { ... }- Specified by:
getForwardPayloadHeaderBytesin interfaceJwtProviderOrBuilder- Returns:
- The bytes for forwardPayloadHeader.
-
setForwardPayloadHeader
This field specifies the header name to forward a successfully verified JWT payload to the backend. The forwarded data is:: base64url_encoded(jwt_payload_in_JSON) If it is not specified, the payload will not be forwarded.string forward_payload_header = 8 [(.validate.rules) = { ... }- Parameters:
value- The forwardPayloadHeader to set.- Returns:
- This builder for chaining.
-
clearForwardPayloadHeader
This field specifies the header name to forward a successfully verified JWT payload to the backend. The forwarded data is:: base64url_encoded(jwt_payload_in_JSON) If it is not specified, the payload will not be forwarded.string forward_payload_header = 8 [(.validate.rules) = { ... }- Returns:
- This builder for chaining.
-
setForwardPayloadHeaderBytes
This field specifies the header name to forward a successfully verified JWT payload to the backend. The forwarded data is:: base64url_encoded(jwt_payload_in_JSON) If it is not specified, the payload will not be forwarded.string forward_payload_header = 8 [(.validate.rules) = { ... }- Parameters:
value- The bytes for forwardPayloadHeader to set.- Returns:
- This builder for chaining.
-
getPadForwardPayloadHeader
public boolean getPadForwardPayloadHeader()When :ref:`forward_payload_header <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.forward_payload_header>` is specified, the base64 encoded payload will be added to the headers. Normally JWT based64 encode doesn't add padding. If this field is true, the header will be padded. This field is only relevant if :ref:`forward_payload_header <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.forward_payload_header>` is specified.
bool pad_forward_payload_header = 11;- Specified by:
getPadForwardPayloadHeaderin interfaceJwtProviderOrBuilder- Returns:
- The padForwardPayloadHeader.
-
setPadForwardPayloadHeader
When :ref:`forward_payload_header <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.forward_payload_header>` is specified, the base64 encoded payload will be added to the headers. Normally JWT based64 encode doesn't add padding. If this field is true, the header will be padded. This field is only relevant if :ref:`forward_payload_header <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.forward_payload_header>` is specified.
bool pad_forward_payload_header = 11;- Parameters:
value- The padForwardPayloadHeader to set.- Returns:
- This builder for chaining.
-
clearPadForwardPayloadHeader
When :ref:`forward_payload_header <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.forward_payload_header>` is specified, the base64 encoded payload will be added to the headers. Normally JWT based64 encode doesn't add padding. If this field is true, the header will be padded. This field is only relevant if :ref:`forward_payload_header <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.forward_payload_header>` is specified.
bool pad_forward_payload_header = 11;- Returns:
- This builder for chaining.
-
getPayloadInMetadata
If non empty, successfully verified JWT payloads will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ````envoy.filters.http.jwt_authn```` The value is the ``protobuf::Struct``. The value of this field will be the key for its ``fields`` and the value is the ``protobuf::Struct`` converted from JWT JSON payload. For example, if payload_in_metadata is ``my_payload``: .. code-block:: yaml envoy.filters.http.jwt_authn: my_payload: iss: https://example.com sub: test@example.com aud: https://example.com exp: 1501281058string payload_in_metadata = 9;- Specified by:
getPayloadInMetadatain interfaceJwtProviderOrBuilder- Returns:
- The payloadInMetadata.
-
getPayloadInMetadataBytes
public com.google.protobuf.ByteString getPayloadInMetadataBytes()If non empty, successfully verified JWT payloads will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ````envoy.filters.http.jwt_authn```` The value is the ``protobuf::Struct``. The value of this field will be the key for its ``fields`` and the value is the ``protobuf::Struct`` converted from JWT JSON payload. For example, if payload_in_metadata is ``my_payload``: .. code-block:: yaml envoy.filters.http.jwt_authn: my_payload: iss: https://example.com sub: test@example.com aud: https://example.com exp: 1501281058string payload_in_metadata = 9;- Specified by:
getPayloadInMetadataBytesin interfaceJwtProviderOrBuilder- Returns:
- The bytes for payloadInMetadata.
-
setPayloadInMetadata
If non empty, successfully verified JWT payloads will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ````envoy.filters.http.jwt_authn```` The value is the ``protobuf::Struct``. The value of this field will be the key for its ``fields`` and the value is the ``protobuf::Struct`` converted from JWT JSON payload. For example, if payload_in_metadata is ``my_payload``: .. code-block:: yaml envoy.filters.http.jwt_authn: my_payload: iss: https://example.com sub: test@example.com aud: https://example.com exp: 1501281058string payload_in_metadata = 9;- Parameters:
value- The payloadInMetadata to set.- Returns:
- This builder for chaining.
-
clearPayloadInMetadata
If non empty, successfully verified JWT payloads will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ````envoy.filters.http.jwt_authn```` The value is the ``protobuf::Struct``. The value of this field will be the key for its ``fields`` and the value is the ``protobuf::Struct`` converted from JWT JSON payload. For example, if payload_in_metadata is ``my_payload``: .. code-block:: yaml envoy.filters.http.jwt_authn: my_payload: iss: https://example.com sub: test@example.com aud: https://example.com exp: 1501281058string payload_in_metadata = 9;- Returns:
- This builder for chaining.
-
setPayloadInMetadataBytes
If non empty, successfully verified JWT payloads will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ````envoy.filters.http.jwt_authn```` The value is the ``protobuf::Struct``. The value of this field will be the key for its ``fields`` and the value is the ``protobuf::Struct`` converted from JWT JSON payload. For example, if payload_in_metadata is ``my_payload``: .. code-block:: yaml envoy.filters.http.jwt_authn: my_payload: iss: https://example.com sub: test@example.com aud: https://example.com exp: 1501281058string payload_in_metadata = 9;- Parameters:
value- The bytes for payloadInMetadata to set.- Returns:
- This builder for chaining.
-
hasNormalizePayloadInMetadata
public boolean hasNormalizePayloadInMetadata()Normalizes the payload representation in the request metadata.
.envoy.extensions.filters.http.jwt_authn.v3.JwtProvider.NormalizePayload normalize_payload_in_metadata = 18;- Specified by:
hasNormalizePayloadInMetadatain interfaceJwtProviderOrBuilder- Returns:
- Whether the normalizePayloadInMetadata field is set.
-
getNormalizePayloadInMetadata
Normalizes the payload representation in the request metadata.
.envoy.extensions.filters.http.jwt_authn.v3.JwtProvider.NormalizePayload normalize_payload_in_metadata = 18;- Specified by:
getNormalizePayloadInMetadatain interfaceJwtProviderOrBuilder- Returns:
- The normalizePayloadInMetadata.
-
setNormalizePayloadInMetadata
Normalizes the payload representation in the request metadata.
.envoy.extensions.filters.http.jwt_authn.v3.JwtProvider.NormalizePayload normalize_payload_in_metadata = 18; -
setNormalizePayloadInMetadata
public JwtProvider.Builder setNormalizePayloadInMetadata(JwtProvider.NormalizePayload.Builder builderForValue) Normalizes the payload representation in the request metadata.
.envoy.extensions.filters.http.jwt_authn.v3.JwtProvider.NormalizePayload normalize_payload_in_metadata = 18; -
mergeNormalizePayloadInMetadata
Normalizes the payload representation in the request metadata.
.envoy.extensions.filters.http.jwt_authn.v3.JwtProvider.NormalizePayload normalize_payload_in_metadata = 18; -
clearNormalizePayloadInMetadata
Normalizes the payload representation in the request metadata.
.envoy.extensions.filters.http.jwt_authn.v3.JwtProvider.NormalizePayload normalize_payload_in_metadata = 18; -
getNormalizePayloadInMetadataBuilder
Normalizes the payload representation in the request metadata.
.envoy.extensions.filters.http.jwt_authn.v3.JwtProvider.NormalizePayload normalize_payload_in_metadata = 18; -
getNormalizePayloadInMetadataOrBuilder
Normalizes the payload representation in the request metadata.
.envoy.extensions.filters.http.jwt_authn.v3.JwtProvider.NormalizePayload normalize_payload_in_metadata = 18;- Specified by:
getNormalizePayloadInMetadataOrBuilderin interfaceJwtProviderOrBuilder
-
getHeaderInMetadata
If not empty, similar to :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>`, a successfully verified JWT header will be written to :ref:`Dynamic State <arch_overview_data_sharing_between_filters>` as an entry (``protobuf::Struct``) in ``envoy.filters.http.jwt_authn`` ``namespace`` with the value of this field as the key. For example, if ``header_in_metadata`` is ``my_header``: .. code-block:: yaml envoy.filters.http.jwt_authn: my_header: alg: JWT kid: EF71iSaosbC5C4tC6Syq1Gm647M alg: PS256 When the metadata has ``envoy.filters.http.jwt_authn`` entry already (for example if :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>` is not empty), it will be inserted as a new entry in the same ``namespace`` as shown below: .. code-block:: yaml envoy.filters.http.jwt_authn: my_payload: iss: https://example.com sub: test@example.com aud: https://example.com exp: 1501281058 my_header: alg: JWT kid: EF71iSaosbC5C4tC6Syq1Gm647M alg: PS256 .. warning:: Using the same key name for :ref:`header_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>` and :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>` is not suggested due to potential override of existing entry, while it is not enforced during config validation.string header_in_metadata = 14;- Specified by:
getHeaderInMetadatain interfaceJwtProviderOrBuilder- Returns:
- The headerInMetadata.
-
getHeaderInMetadataBytes
public com.google.protobuf.ByteString getHeaderInMetadataBytes()If not empty, similar to :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>`, a successfully verified JWT header will be written to :ref:`Dynamic State <arch_overview_data_sharing_between_filters>` as an entry (``protobuf::Struct``) in ``envoy.filters.http.jwt_authn`` ``namespace`` with the value of this field as the key. For example, if ``header_in_metadata`` is ``my_header``: .. code-block:: yaml envoy.filters.http.jwt_authn: my_header: alg: JWT kid: EF71iSaosbC5C4tC6Syq1Gm647M alg: PS256 When the metadata has ``envoy.filters.http.jwt_authn`` entry already (for example if :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>` is not empty), it will be inserted as a new entry in the same ``namespace`` as shown below: .. code-block:: yaml envoy.filters.http.jwt_authn: my_payload: iss: https://example.com sub: test@example.com aud: https://example.com exp: 1501281058 my_header: alg: JWT kid: EF71iSaosbC5C4tC6Syq1Gm647M alg: PS256 .. warning:: Using the same key name for :ref:`header_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>` and :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>` is not suggested due to potential override of existing entry, while it is not enforced during config validation.string header_in_metadata = 14;- Specified by:
getHeaderInMetadataBytesin interfaceJwtProviderOrBuilder- Returns:
- The bytes for headerInMetadata.
-
setHeaderInMetadata
If not empty, similar to :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>`, a successfully verified JWT header will be written to :ref:`Dynamic State <arch_overview_data_sharing_between_filters>` as an entry (``protobuf::Struct``) in ``envoy.filters.http.jwt_authn`` ``namespace`` with the value of this field as the key. For example, if ``header_in_metadata`` is ``my_header``: .. code-block:: yaml envoy.filters.http.jwt_authn: my_header: alg: JWT kid: EF71iSaosbC5C4tC6Syq1Gm647M alg: PS256 When the metadata has ``envoy.filters.http.jwt_authn`` entry already (for example if :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>` is not empty), it will be inserted as a new entry in the same ``namespace`` as shown below: .. code-block:: yaml envoy.filters.http.jwt_authn: my_payload: iss: https://example.com sub: test@example.com aud: https://example.com exp: 1501281058 my_header: alg: JWT kid: EF71iSaosbC5C4tC6Syq1Gm647M alg: PS256 .. warning:: Using the same key name for :ref:`header_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>` and :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>` is not suggested due to potential override of existing entry, while it is not enforced during config validation.string header_in_metadata = 14;- Parameters:
value- The headerInMetadata to set.- Returns:
- This builder for chaining.
-
clearHeaderInMetadata
If not empty, similar to :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>`, a successfully verified JWT header will be written to :ref:`Dynamic State <arch_overview_data_sharing_between_filters>` as an entry (``protobuf::Struct``) in ``envoy.filters.http.jwt_authn`` ``namespace`` with the value of this field as the key. For example, if ``header_in_metadata`` is ``my_header``: .. code-block:: yaml envoy.filters.http.jwt_authn: my_header: alg: JWT kid: EF71iSaosbC5C4tC6Syq1Gm647M alg: PS256 When the metadata has ``envoy.filters.http.jwt_authn`` entry already (for example if :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>` is not empty), it will be inserted as a new entry in the same ``namespace`` as shown below: .. code-block:: yaml envoy.filters.http.jwt_authn: my_payload: iss: https://example.com sub: test@example.com aud: https://example.com exp: 1501281058 my_header: alg: JWT kid: EF71iSaosbC5C4tC6Syq1Gm647M alg: PS256 .. warning:: Using the same key name for :ref:`header_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>` and :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>` is not suggested due to potential override of existing entry, while it is not enforced during config validation.string header_in_metadata = 14;- Returns:
- This builder for chaining.
-
setHeaderInMetadataBytes
If not empty, similar to :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>`, a successfully verified JWT header will be written to :ref:`Dynamic State <arch_overview_data_sharing_between_filters>` as an entry (``protobuf::Struct``) in ``envoy.filters.http.jwt_authn`` ``namespace`` with the value of this field as the key. For example, if ``header_in_metadata`` is ``my_header``: .. code-block:: yaml envoy.filters.http.jwt_authn: my_header: alg: JWT kid: EF71iSaosbC5C4tC6Syq1Gm647M alg: PS256 When the metadata has ``envoy.filters.http.jwt_authn`` entry already (for example if :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>` is not empty), it will be inserted as a new entry in the same ``namespace`` as shown below: .. code-block:: yaml envoy.filters.http.jwt_authn: my_payload: iss: https://example.com sub: test@example.com aud: https://example.com exp: 1501281058 my_header: alg: JWT kid: EF71iSaosbC5C4tC6Syq1Gm647M alg: PS256 .. warning:: Using the same key name for :ref:`header_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>` and :ref:`payload_in_metadata <envoy_v3_api_field_extensions.filters.http.jwt_authn.v3.JwtProvider.payload_in_metadata>` is not suggested due to potential override of existing entry, while it is not enforced during config validation.string header_in_metadata = 14;- Parameters:
value- The bytes for headerInMetadata to set.- Returns:
- This builder for chaining.
-
getFailedStatusInMetadata
If non empty, the failure status ``::google::jwt_verify::Status`` for a non verified JWT will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ``envoy.filters.http.jwt_authn`` The value is the ``protobuf::Struct``. The values of this field will be ``code`` and ``message`` and they will contain the JWT authentication failure status code and a message describing the failure. For example, if failed_status_in_metadata is ``my_auth_failure_status``: .. code-block:: yaml envoy.filters.http.jwt_authn: my_auth_failure_status: code: 3 message: Jwt expiredstring failed_status_in_metadata = 16;- Specified by:
getFailedStatusInMetadatain interfaceJwtProviderOrBuilder- Returns:
- The failedStatusInMetadata.
-
getFailedStatusInMetadataBytes
public com.google.protobuf.ByteString getFailedStatusInMetadataBytes()If non empty, the failure status ``::google::jwt_verify::Status`` for a non verified JWT will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ``envoy.filters.http.jwt_authn`` The value is the ``protobuf::Struct``. The values of this field will be ``code`` and ``message`` and they will contain the JWT authentication failure status code and a message describing the failure. For example, if failed_status_in_metadata is ``my_auth_failure_status``: .. code-block:: yaml envoy.filters.http.jwt_authn: my_auth_failure_status: code: 3 message: Jwt expiredstring failed_status_in_metadata = 16;- Specified by:
getFailedStatusInMetadataBytesin interfaceJwtProviderOrBuilder- Returns:
- The bytes for failedStatusInMetadata.
-
setFailedStatusInMetadata
If non empty, the failure status ``::google::jwt_verify::Status`` for a non verified JWT will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ``envoy.filters.http.jwt_authn`` The value is the ``protobuf::Struct``. The values of this field will be ``code`` and ``message`` and they will contain the JWT authentication failure status code and a message describing the failure. For example, if failed_status_in_metadata is ``my_auth_failure_status``: .. code-block:: yaml envoy.filters.http.jwt_authn: my_auth_failure_status: code: 3 message: Jwt expiredstring failed_status_in_metadata = 16;- Parameters:
value- The failedStatusInMetadata to set.- Returns:
- This builder for chaining.
-
clearFailedStatusInMetadata
If non empty, the failure status ``::google::jwt_verify::Status`` for a non verified JWT will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ``envoy.filters.http.jwt_authn`` The value is the ``protobuf::Struct``. The values of this field will be ``code`` and ``message`` and they will contain the JWT authentication failure status code and a message describing the failure. For example, if failed_status_in_metadata is ``my_auth_failure_status``: .. code-block:: yaml envoy.filters.http.jwt_authn: my_auth_failure_status: code: 3 message: Jwt expiredstring failed_status_in_metadata = 16;- Returns:
- This builder for chaining.
-
setFailedStatusInMetadataBytes
If non empty, the failure status ``::google::jwt_verify::Status`` for a non verified JWT will be written to StreamInfo DynamicMetadata in the format as: ``namespace`` is the jwt_authn filter name as ``envoy.filters.http.jwt_authn`` The value is the ``protobuf::Struct``. The values of this field will be ``code`` and ``message`` and they will contain the JWT authentication failure status code and a message describing the failure. For example, if failed_status_in_metadata is ``my_auth_failure_status``: .. code-block:: yaml envoy.filters.http.jwt_authn: my_auth_failure_status: code: 3 message: Jwt expiredstring failed_status_in_metadata = 16;- Parameters:
value- The bytes for failedStatusInMetadata to set.- Returns:
- This builder for chaining.
-
getClockSkewSeconds
public int getClockSkewSeconds()Specify the clock skew in seconds when verifying JWT time constraint, such as ``exp``, and ``nbf``. If not specified, default is 60 seconds.
uint32 clock_skew_seconds = 10;- Specified by:
getClockSkewSecondsin interfaceJwtProviderOrBuilder- Returns:
- The clockSkewSeconds.
-
setClockSkewSeconds
Specify the clock skew in seconds when verifying JWT time constraint, such as ``exp``, and ``nbf``. If not specified, default is 60 seconds.
uint32 clock_skew_seconds = 10;- Parameters:
value- The clockSkewSeconds to set.- Returns:
- This builder for chaining.
-
clearClockSkewSeconds
Specify the clock skew in seconds when verifying JWT time constraint, such as ``exp``, and ``nbf``. If not specified, default is 60 seconds.
uint32 clock_skew_seconds = 10;- Returns:
- This builder for chaining.
-
hasJwtCacheConfig
public boolean hasJwtCacheConfig()Enables JWT cache, its size is specified by ``jwt_cache_size``. Only valid JWTs are cached.
.envoy.extensions.filters.http.jwt_authn.v3.JwtCacheConfig jwt_cache_config = 12;- Specified by:
hasJwtCacheConfigin interfaceJwtProviderOrBuilder- Returns:
- Whether the jwtCacheConfig field is set.
-
getJwtCacheConfig
Enables JWT cache, its size is specified by ``jwt_cache_size``. Only valid JWTs are cached.
.envoy.extensions.filters.http.jwt_authn.v3.JwtCacheConfig jwt_cache_config = 12;- Specified by:
getJwtCacheConfigin interfaceJwtProviderOrBuilder- Returns:
- The jwtCacheConfig.
-
setJwtCacheConfig
Enables JWT cache, its size is specified by ``jwt_cache_size``. Only valid JWTs are cached.
.envoy.extensions.filters.http.jwt_authn.v3.JwtCacheConfig jwt_cache_config = 12; -
setJwtCacheConfig
Enables JWT cache, its size is specified by ``jwt_cache_size``. Only valid JWTs are cached.
.envoy.extensions.filters.http.jwt_authn.v3.JwtCacheConfig jwt_cache_config = 12; -
mergeJwtCacheConfig
Enables JWT cache, its size is specified by ``jwt_cache_size``. Only valid JWTs are cached.
.envoy.extensions.filters.http.jwt_authn.v3.JwtCacheConfig jwt_cache_config = 12; -
clearJwtCacheConfig
Enables JWT cache, its size is specified by ``jwt_cache_size``. Only valid JWTs are cached.
.envoy.extensions.filters.http.jwt_authn.v3.JwtCacheConfig jwt_cache_config = 12; -
getJwtCacheConfigBuilder
Enables JWT cache, its size is specified by ``jwt_cache_size``. Only valid JWTs are cached.
.envoy.extensions.filters.http.jwt_authn.v3.JwtCacheConfig jwt_cache_config = 12; -
getJwtCacheConfigOrBuilder
Enables JWT cache, its size is specified by ``jwt_cache_size``. Only valid JWTs are cached.
.envoy.extensions.filters.http.jwt_authn.v3.JwtCacheConfig jwt_cache_config = 12;- Specified by:
getJwtCacheConfigOrBuilderin interfaceJwtProviderOrBuilder
-
getClaimToHeadersList
Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header. For examples, following config: The claim must be of type; string, int, double, bool. Array type claims are not supported .. literalinclude:: /_configs/repo/jwt_authn.yaml :language: yaml :lines: 44-48 :linenos: :lineno-start: 44 :caption: :download:`jwt_authn.yaml </_configs/repo/jwt_authn.yaml>` This header is only reserved for jwt claim; any other value will be overwritten.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtClaimToHeader claim_to_headers = 15;- Specified by:
getClaimToHeadersListin interfaceJwtProviderOrBuilder
-
getClaimToHeadersCount
public int getClaimToHeadersCount()Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header. For examples, following config: The claim must be of type; string, int, double, bool. Array type claims are not supported .. literalinclude:: /_configs/repo/jwt_authn.yaml :language: yaml :lines: 44-48 :linenos: :lineno-start: 44 :caption: :download:`jwt_authn.yaml </_configs/repo/jwt_authn.yaml>` This header is only reserved for jwt claim; any other value will be overwritten.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtClaimToHeader claim_to_headers = 15;- Specified by:
getClaimToHeadersCountin interfaceJwtProviderOrBuilder
-
getClaimToHeaders
Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header. For examples, following config: The claim must be of type; string, int, double, bool. Array type claims are not supported .. literalinclude:: /_configs/repo/jwt_authn.yaml :language: yaml :lines: 44-48 :linenos: :lineno-start: 44 :caption: :download:`jwt_authn.yaml </_configs/repo/jwt_authn.yaml>` This header is only reserved for jwt claim; any other value will be overwritten.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtClaimToHeader claim_to_headers = 15;- Specified by:
getClaimToHeadersin interfaceJwtProviderOrBuilder
-
setClaimToHeaders
Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header. For examples, following config: The claim must be of type; string, int, double, bool. Array type claims are not supported .. literalinclude:: /_configs/repo/jwt_authn.yaml :language: yaml :lines: 44-48 :linenos: :lineno-start: 44 :caption: :download:`jwt_authn.yaml </_configs/repo/jwt_authn.yaml>` This header is only reserved for jwt claim; any other value will be overwritten.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtClaimToHeader claim_to_headers = 15; -
setClaimToHeaders
Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header. For examples, following config: The claim must be of type; string, int, double, bool. Array type claims are not supported .. literalinclude:: /_configs/repo/jwt_authn.yaml :language: yaml :lines: 44-48 :linenos: :lineno-start: 44 :caption: :download:`jwt_authn.yaml </_configs/repo/jwt_authn.yaml>` This header is only reserved for jwt claim; any other value will be overwritten.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtClaimToHeader claim_to_headers = 15; -
addClaimToHeaders
Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header. For examples, following config: The claim must be of type; string, int, double, bool. Array type claims are not supported .. literalinclude:: /_configs/repo/jwt_authn.yaml :language: yaml :lines: 44-48 :linenos: :lineno-start: 44 :caption: :download:`jwt_authn.yaml </_configs/repo/jwt_authn.yaml>` This header is only reserved for jwt claim; any other value will be overwritten.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtClaimToHeader claim_to_headers = 15; -
addClaimToHeaders
Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header. For examples, following config: The claim must be of type; string, int, double, bool. Array type claims are not supported .. literalinclude:: /_configs/repo/jwt_authn.yaml :language: yaml :lines: 44-48 :linenos: :lineno-start: 44 :caption: :download:`jwt_authn.yaml </_configs/repo/jwt_authn.yaml>` This header is only reserved for jwt claim; any other value will be overwritten.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtClaimToHeader claim_to_headers = 15; -
addClaimToHeaders
Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header. For examples, following config: The claim must be of type; string, int, double, bool. Array type claims are not supported .. literalinclude:: /_configs/repo/jwt_authn.yaml :language: yaml :lines: 44-48 :linenos: :lineno-start: 44 :caption: :download:`jwt_authn.yaml </_configs/repo/jwt_authn.yaml>` This header is only reserved for jwt claim; any other value will be overwritten.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtClaimToHeader claim_to_headers = 15; -
addClaimToHeaders
Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header. For examples, following config: The claim must be of type; string, int, double, bool. Array type claims are not supported .. literalinclude:: /_configs/repo/jwt_authn.yaml :language: yaml :lines: 44-48 :linenos: :lineno-start: 44 :caption: :download:`jwt_authn.yaml </_configs/repo/jwt_authn.yaml>` This header is only reserved for jwt claim; any other value will be overwritten.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtClaimToHeader claim_to_headers = 15; -
addAllClaimToHeaders
Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header. For examples, following config: The claim must be of type; string, int, double, bool. Array type claims are not supported .. literalinclude:: /_configs/repo/jwt_authn.yaml :language: yaml :lines: 44-48 :linenos: :lineno-start: 44 :caption: :download:`jwt_authn.yaml </_configs/repo/jwt_authn.yaml>` This header is only reserved for jwt claim; any other value will be overwritten.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtClaimToHeader claim_to_headers = 15; -
clearClaimToHeaders
Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header. For examples, following config: The claim must be of type; string, int, double, bool. Array type claims are not supported .. literalinclude:: /_configs/repo/jwt_authn.yaml :language: yaml :lines: 44-48 :linenos: :lineno-start: 44 :caption: :download:`jwt_authn.yaml </_configs/repo/jwt_authn.yaml>` This header is only reserved for jwt claim; any other value will be overwritten.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtClaimToHeader claim_to_headers = 15; -
removeClaimToHeaders
Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header. For examples, following config: The claim must be of type; string, int, double, bool. Array type claims are not supported .. literalinclude:: /_configs/repo/jwt_authn.yaml :language: yaml :lines: 44-48 :linenos: :lineno-start: 44 :caption: :download:`jwt_authn.yaml </_configs/repo/jwt_authn.yaml>` This header is only reserved for jwt claim; any other value will be overwritten.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtClaimToHeader claim_to_headers = 15; -
getClaimToHeadersBuilder
Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header. For examples, following config: The claim must be of type; string, int, double, bool. Array type claims are not supported .. literalinclude:: /_configs/repo/jwt_authn.yaml :language: yaml :lines: 44-48 :linenos: :lineno-start: 44 :caption: :download:`jwt_authn.yaml </_configs/repo/jwt_authn.yaml>` This header is only reserved for jwt claim; any other value will be overwritten.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtClaimToHeader claim_to_headers = 15; -
getClaimToHeadersOrBuilder
Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header. For examples, following config: The claim must be of type; string, int, double, bool. Array type claims are not supported .. literalinclude:: /_configs/repo/jwt_authn.yaml :language: yaml :lines: 44-48 :linenos: :lineno-start: 44 :caption: :download:`jwt_authn.yaml </_configs/repo/jwt_authn.yaml>` This header is only reserved for jwt claim; any other value will be overwritten.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtClaimToHeader claim_to_headers = 15;- Specified by:
getClaimToHeadersOrBuilderin interfaceJwtProviderOrBuilder
-
getClaimToHeadersOrBuilderList
Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header. For examples, following config: The claim must be of type; string, int, double, bool. Array type claims are not supported .. literalinclude:: /_configs/repo/jwt_authn.yaml :language: yaml :lines: 44-48 :linenos: :lineno-start: 44 :caption: :download:`jwt_authn.yaml </_configs/repo/jwt_authn.yaml>` This header is only reserved for jwt claim; any other value will be overwritten.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtClaimToHeader claim_to_headers = 15;- Specified by:
getClaimToHeadersOrBuilderListin interfaceJwtProviderOrBuilder
-
addClaimToHeadersBuilder
Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header. For examples, following config: The claim must be of type; string, int, double, bool. Array type claims are not supported .. literalinclude:: /_configs/repo/jwt_authn.yaml :language: yaml :lines: 44-48 :linenos: :lineno-start: 44 :caption: :download:`jwt_authn.yaml </_configs/repo/jwt_authn.yaml>` This header is only reserved for jwt claim; any other value will be overwritten.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtClaimToHeader claim_to_headers = 15; -
addClaimToHeadersBuilder
Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header. For examples, following config: The claim must be of type; string, int, double, bool. Array type claims are not supported .. literalinclude:: /_configs/repo/jwt_authn.yaml :language: yaml :lines: 44-48 :linenos: :lineno-start: 44 :caption: :download:`jwt_authn.yaml </_configs/repo/jwt_authn.yaml>` This header is only reserved for jwt claim; any other value will be overwritten.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtClaimToHeader claim_to_headers = 15; -
getClaimToHeadersBuilderList
Add JWT claim to HTTP Header Specify the claim name you want to copy in which HTTP header. For examples, following config: The claim must be of type; string, int, double, bool. Array type claims are not supported .. literalinclude:: /_configs/repo/jwt_authn.yaml :language: yaml :lines: 44-48 :linenos: :lineno-start: 44 :caption: :download:`jwt_authn.yaml </_configs/repo/jwt_authn.yaml>` This header is only reserved for jwt claim; any other value will be overwritten.repeated .envoy.extensions.filters.http.jwt_authn.v3.JwtClaimToHeader claim_to_headers = 15; -
getClearRouteCache
public boolean getClearRouteCache()Clears route cache in order to allow the JWT to correctly affect routing decisions. Filter clears all cached routes when: 1. The field is set to ``true``. 2. At least one ``claim_to_headers`` header is added to the request OR if ``payload_in_metadata`` is set.bool clear_route_cache = 17;- Specified by:
getClearRouteCachein interfaceJwtProviderOrBuilder- Returns:
- The clearRouteCache.
-
setClearRouteCache
Clears route cache in order to allow the JWT to correctly affect routing decisions. Filter clears all cached routes when: 1. The field is set to ``true``. 2. At least one ``claim_to_headers`` header is added to the request OR if ``payload_in_metadata`` is set.bool clear_route_cache = 17;- Parameters:
value- The clearRouteCache to set.- Returns:
- This builder for chaining.
-
clearClearRouteCache
Clears route cache in order to allow the JWT to correctly affect routing decisions. Filter clears all cached routes when: 1. The field is set to ``true``. 2. At least one ``claim_to_headers`` header is added to the request OR if ``payload_in_metadata`` is set.bool clear_route_cache = 17;- Returns:
- This builder for chaining.
-
setUnknownFields
public final JwtProvider.Builder setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) - Specified by:
setUnknownFieldsin interfacecom.google.protobuf.Message.Builder- Overrides:
setUnknownFieldsin classcom.google.protobuf.GeneratedMessageV3.Builder<JwtProvider.Builder>
-
mergeUnknownFields
public final JwtProvider.Builder mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) - Specified by:
mergeUnknownFieldsin interfacecom.google.protobuf.Message.Builder- Overrides:
mergeUnknownFieldsin classcom.google.protobuf.GeneratedMessageV3.Builder<JwtProvider.Builder>
-