OAuth2 plan with cache resource not working

[exalate-issue-sync]

[[ | #describe-the-bug-describe-the-bug-]| #-describe-the-bug-describe-the-bug-describe-the-bug-describe-the-bug]describe-the-bug-Describe the bug :

We have an API with OAuth 2 plan which is using Cache resource. We have the Propagate Authorization Header off. In Design when using the

{#context.attributes['oauth.client_id']}

EL in Transform Headers with scope Request the value is not being retrieved while on Request_Content it is. If we remove the Cache there is no issue at all for all scopes.

[[ | #to-reproduce-to-reproduce-]| #-to-reproduce-to-reproduce-to-reproduce-to-reproduce]to-reproduce-To Reproduce :

Steps to reproduce the behavior:

1. Setup AM so it can be used in this API.
2. Import the API share in this ticket and only change the AM resource to fit your own.
3. Send a request to the API with Cache and without Cache or with Cache but change the scope on Transform Header policy.
4. See error

[[ | #expected-behavior-expected-behavior-]| #-expected-behavior-expected-behavior-expected-behavior-expected-behavior]expected-behavior-Expected behavior :

The Cache should not change the behavior of the OAuth 2 Plan and the policy usage.

[[ | #useful-information-useful-information-]| #-useful-information-useful-information-useful-information-useful-information]useful-information-Useful information :

API attached to the ticket.

[[ | #desktop-desktop-]| #-desktop-desktop-desktop-desktop]desktop-Desktop :

• Environment: APIM 3.15, 3.18, 3.20 Docker-Desktop
• Browser: Google Chrome

[[ | #attachmentsattachments]| #--attachmentsattachmentsattachmentsattachments]attachmentsAttachments

Echo-1 (7).json

[exalate-issue-sync]

This issue has been fixed in versions 3.20.20

[Mattiamato]

Will this be documented in https://docs.gravitee.io/apim/3.x/changelog-3.20.html ?

[marijatimovska]

This issue has been fixed in versions 3.20.21

[phiz71]

Will this be documented in docs.gravitee.io/apim/3.x/changelog-3.20.html ?

Hello @Mattiamato,
Yes it will be, after the 3.20.21 is released.

There has been a little error when we put the first fixed version. It's not 3.20.20 but 3.20.21.