Header Forwarding

[maaft]

I have multiple GraphQL servers which require token authentification. Unfortunately, graphql-mesh seems to drop any headers sent from the client.

Is it possible to forward any given authentication tokens (or headers in general) to the different GQL servers?

[ardatan]

Actually GraphQL Mesh doesn't drop the headers because it is not a server :) It is a library that generates a GraphQL Schema for you and mesh serve binds this schema to HTTP(the schema may not be used via HTTP because it is generated as a local executable schema even with graphql-js). So you are the responsible of handling authentication.

If you stick with mesh serve which uses express-graphql and returns request object as it is, you can forward headers like below;

sources:
  - name: SomeEndpoint
     handler:
        graphql:
           endpoint: ....
           operationHeaders: 
                Authorization: "{context.headers.Authorization}"

or you can pass it using arguments;

sources:
  - name: SomeEndpoint
     handler:
        graphql:
           endpoint: ....
           operationHeaders: 
                Authorization: Bearer {args.someApiKey}

[maaft]

I tried it with the first approach and I am just receiving the following at my endpoint:

{
  accept: 'application/json',
  'content-type': 'application/json',
  authorization: '{context.headers.Authorization}',
  'content-length': '63',
  'user-agent': 'node-fetch/1.0 (+https://github.com/bitinn/node-fetch)',
  'accept-encoding': 'gzip,deflate',
  connection: 'close',
  host: 'localhost:4001'
}

[maaft]

When I ommit the quotes " ", instead I receive the following:

{
  accept: 'application/json',
  'content-type': 'application/json',
  authorization: '[object Object]',
  'content-length': '63',
  'user-agent': 'node-fetch/1.0 (+https://github.com/bitinn/node-fetch)',
  'accept-encoding': 'gzip,deflate',
  connection: 'close',
  host: 'localhost:4001'
}

[ardatan]

This should be fixed in the latest version. If it still persists, feel
free to submit an issue with a reproduction.

[maaft]

When using:
Authorization: "${context.headers.authorization}", I get an empty string on my server. Which makes me believe that the request ist not added to the context.

Therefore, I guess the real question is:
How can I add the headers to my context using graphql-mesh?

[ardatan]

When you add $, yaml parser thinks it is an environmental variable. So it won't work. You can create your own GraphQL server that serves Mesh's schema as in the examples.

[byteninja]

Same here seems that the interpolation does not work in the headers field of an graphql endpoint
with an openapi endpoint this works perfect

[ardatan]

This should be fixed in the latest version.