Is there a way to pass headers for Subscription?

[vasily-polonsky]

Hi there, I am using mesh + yoga. And forwarding headers to yoga and back via the plugin described here #4967. And how I have a need to add headers, or somehow pass context from mesh to yoga in one direction only. It's not about forwarding the header from a client, mesh gets the user in AuthPlugin and I want to pass the header or whatever with "currentUser" yoga, but wasn't able to find a way to do that. Hope for your help

[ardatan]

It depends on which transport you use. If you use SSE, operationHeaders is enough. If you use WS, you need to use connectionParams.

[vasily-polonsky]

Thank you for such quick response. Yes, I use WS, I tried to set connectionParams in .meshrc.yaml, but they are passed as a string, I made it like here #5774 , the issue is closed but I still face this issue, probably because the fix is not released. Or I am doing smt wrong?

[vasily-polonsky]

What do you mean by "as a string"?

I mean, when I use WS as a subscription protocol, and set connectionParams in mesh configuration

subscriptionsProtocol: WS connectionParams: Authorization: "{context.headers['authorization']}" Auth: "{context.connectionParams['authorization']}"

In yoga I receive exactly these strings, they are not resolved to a value. Getting this result even after I updated library @graphql-tools/executor-graphql-ws to the latest 1.1.1 version

You don't need to install GraphQL SSE plugin especially for the GW and the service communication. Yoga has built-in support for SSE.

Yeah, that's true and with a basic setup it works, but I wanted a more advanced setup described here https://the-guild.dev/graphql/yoga-server/docs/features/subscriptions . To overcome 6 distinct connectections issue with HTTP/1
I tried to connect mesh with yoga + subscribptions over /graphql/stream endpoint but wasn't able to make it run and also wasn't able to find any examples of such setup on the internet

[ardatan]

You can use subscriptionsEndpoint to define the endpoint for subscriptions;

In yoga I receive exactly these strings, they are not resolved to a value. Getting this result even after I updated library @graphql-tools/executor-graphql-ws to the latest 1.1.1 version

We'd love to help you if you could create a reproduction on CodeSandbox :) Thanks!

[vasily-polonsky]

In this issue #5774 author created a reproduction on CodeSandbox https://codesandbox.io/p/sandbox/github/roeb/graphql-mesh-apollo-sample/tree/main and github repo. Installing @graphql-tools/executor-graphql-ws@1.1.1 doesnt fix connectionParams. At least it didn't work for me.

[enisdenjo]

The actual problem here is much more complicated. The WebSocket instance in Mesh is instantiated during initialisation providing the connectionParams, and then that client instance is used during execution.

If this weren't so, each subscription would create a new WebSocket connection itself - which is not ideal.

Issue to track: #6335.