To explain how to apply "JWT validation" policy and "OAuth 2.0 access token enforcement using Mule OAuth provider" policy for an API Instance.
UseCase - You have implemented OAuth Provider module and have a requirement to pass JWT token generated from another system to the API.
Pre-requisites:
1) Assume the API Instance is already created in API Manager
2) Assume the JWT token can be generated/retrieved using an external provider
OAuth 2.0 access token enforcement using Mule OAuth provider policy uses below to parse the token.
#[attributes.headers['authorization']]
JWT validation policy also uses below to parse the token.
attributes.headers.authorizationNow it is not possible to pass 2 different authorization token in the same request.
JWT validation policy has a field "JWT Origin" where you can specify Custom Expression instead of the default HTTP Bearer Authentication Header
#[attributes.headers.authorization]
#[attributes.headers['jwt_token']]
001115858

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.