gRPC / ConnectRPC Subgraphs Do Not Receive Propagated Headers from Router

[urosbelov]

Component(s)

router

Component version

0.265.2

wgc version

0.94.4

controlplane version

cloud

router version

0.265.2

What happened?

When using ConnectRPC (gRPC) subgraphs, the router does not propagate any GraphQL client headers to the gRPC downstream services, even though the router configuration includes valid headers.all.request propagation rules.

The same configuration works correctly for HTTP subgraphs, but fails for gRPC subgraphs.

This indicates that header propagation is only implemented for HTTP subgraphs, not gRPC.

Environment information

Environment

OS: (e.g., "Mac OS")
Package Manager: npm

Router configuration

version: "1"

log_level: "debug"
dev_mode: true
execution_config:
  file:
    path: "router.json"
    watch: true
graph:
  token: ""

headers:
  all:
    request:
      - op: "propagate"
        named: "X-User-Id"
      - op: "propagate"
        named: "X-Workspace-Id"
      - op: "propagate"
        named: "Authorization"

Router execution config

version: 1
subgraphs:
  - name: post-service
    routing_url: dns:///localhost:4003
    grpc:
      schema_file: ../services/post-service/src/graph/schema.graphql
      proto_file: ../services/post-service/src/proto/service/v1/service.proto
      mapping_file: ../services/post-service/src/proto/service/v1/mapping.json

Log output

Additional context

No response

[github-actions]

WunderGraph commits fully to Open Source and we want to make sure that we can help you as fast as possible.
The roadmap is driven by our customers and we have to prioritize issues that are important to them.
You can influence the priority by becoming a customer. Please contact us here.

[satvik2131]

Hi @urosbelov, can i work on this issues, if yes please assign this to me. Thanks

[bsuffern]

We have the same issue. We are trying to implement RBAC on all of our gRPC subgraphs using a bearer token passed into the router request which is expected to be propagated to our gRPC services. If there is a workaround if you could let us know that would be great.

[Noroth]

hi @urosbelov,
Thank you for raising this issue. We actually have this on our roadmap already. We are currently working on improving the existing logic for the normal subgraph and the grpc subgraph transport. Therefore we decided to not yet work on it because we would have to refactor it again.

We will be working on this very soon.

[danielgrath]

Great to hear that you have this on the roadmap, we also need this. Could there be a workaround with a custom router module in the meantime? Or is that not possible?