Authorizing websocket connection with connectionParams

[devmentality0]

Hello!
I'm trying to connect my graphql server to remote schema following this example: https://www.graphql-tools.com/docs/remote-schemas#using-graphql-ws
My case is slightly more complex as the remote server requires authorization header with token. I tried to implement it this way:

const wsExecutor: Executor = ({ document, variables, context }) => {
  const subscriptionClient = createClient({
    url: WS_ENDPOINT,
    webSocketImpl: ws,
    connectionParams: {
      headers: {
        authorization: context?.req.headers.authorization
      }
    }
  });

  return observableToAsyncIterable({
    ... /* the same as in the example */
  });
};

With that approach, I encountered a problem: connectionParams are not sent when the client connects to the server.
I was expecting it to be passed somewhere here:

graphql-ws/src/client.ts

Line 593 in 2160755

const socket = new WebSocketImpl(

Is it intended behaviour? Is there any other way to pass authorization header to websocket connection? Thanks!

[enisdenjo]

You cannot provide custom headers to a WebSocket upgrade request.

The connectionParams is the payload part of the ConnectionInit message inside an established WebSocket connection and is available on the server through the Context. Read the "ws server and client auth usage with token expiration, validation and refresh" recipe for inspiration.

Furthermore, please also read: graphql/graphql-over-http#140 (comment).