JSON Web Token (JWT) token format for authentication as defined by
RFC 7519. See OAuth 2.0 and
OIDC 1.0 for how this is used in the whole
Spec for a JWT that is issued by https://example.com, with the audience claims must be either
bookstore_android.apps.example.com or bookstore_web.apps.example.com.
The token should be presented at the Authorization header (default). The Json web key set (JWKS)
will be discovered followwing OpenID Connect protocol.
List of query parameters from which JWT is expected. For example, if JWT is provided via query
parameter my_token (e.g /path?my_token=), the config is:
This field specifies the header name to output a successfully verified JWT payload to the
backend. The forwarded data is base64_encoded(jwt_payload_in_JSON). If it is not specified,
the payload will not be emitted.
If set to true, the orginal token will be kept for the ustream request. Default is false.
This message specifies a header location to extract JWT token.
The HTTP header name.
The prefix that should be stripped before decoding the token.
For example, for “Authorization: Bearer ”, prefix=“Bearer ” with a space at the end.
If the header doesn’t have this exact prefix, it is considerred invalid.