Ustream Header "X-Anonymous-Consumer": "true" is set even if authentication with jwt token was successfully

[Gruummy]

Documentation of the official "jwt" plugin clearly tells that this header should only be true if anonymous access was used to forward the request.
(This plugin here is only a "Extension" of the official "jwt" kong plugin ... and should follow the base functionality of it)

see: https://docs.konghq.com/hub/kong-inc/jwt/

I my testcases i can see for example the following on the upstream service behind kong:

"X-Anonymous-Consumer": "true", "X-Consumer-Custom-Id": "f2cd6020-e3b3-4027-ab3e-968e7c436ef6", "X-Consumer-Id": "bb91d867-66ff-4f51-8d92-8c35a13efee5", "X-Consumer-Username": "f2cd6020-e3b3-4027-ab3e-968e7c436ef6",

Here you can see that a consumer user was used and authenticated .. so "X-Anonymous-Consumer" should be "false" in this case .... or the header probably not exist at all. I personally would vote to have the header with the value "false".

[Gruummy]

Investigation on other plugins for kong showed that here meanwhile code logics had been changed.
I am not sure if with the merge request which is already done .. this not already is solved.

But when i rework the integrationtests in general about the keycloak 18 test issue ... i will add for this situation also a test with the behaviour like it should be ... from kongs perspective.