envoy api-gateway reqId not forwarded by default

[dallas-fletchall]

What product are you having troubles with?

Console

What Console version are you using?

Mia-Platform v14.5.3

Description

The default ext_authz configuration does not seem to forward request ID via header in the api-gateway-envoy-config.

---

Our ext_auth path is:

flowchart LR
    A[api-gateway] --> B[authorization-service] --> C[jwt-token-validator]

Loading

Without the reqId as a header to the authorization-service, there is no x-request-id and/or request-id headers to forward via HEADERS_TO_PROXY. This results in different reqIds for the api-gateway, authorization-service, and jwt-token-validator.

---

Looking at external-authorization docs, I was able to overwrite the configuration adding the headers and verify correlation between all three services in the ext_authz pipeline via logs. Below are the additions that I added:

- listener_name: frontend
   ...
      authorization_request:
        headers_to_add:
        - key: X-Request-Id
          value: '%REQ(X-REQUEST-ID)%'
        - key: Request-Id
          value: '%REQ(X-REQUEST-ID)%'
        ...

Actual Outcome

We are unable to correlate the logs between the api-gateway, authorization-service, and the jwt-token-validator with the default api-gateway configuration.

Expected Outcome

reqId correlation in logs between our ext_authz pipeline.

[dallas-fletchall]

A similar discussion can be found #576, but we are NOT using the custom-plugin-lib.

Additionally, we have validated setup from #576 (comment).

[nicola88]

@dallas-fletchall we are investigating the issue, we will get back when we have updates