buildSubgraphSchema with Apollo federation and authChecker?

[k-atama]

I am using Apollo federation with type-graphql. This works, so far, by building the schema using type-graphqls buildSchema, and then passing the build schema into the buildSubgraphSchema, as well as an set of custom resolvers.

...

const schema = await buildSchema({
    resolvers,
    container: Container,
    // authChecker doesn't seem to be called :/ 
    authChecker: simpleAuthChecker,
  });

  const server = new Server({
    schema: buildSubgraphSchema({
      typeDefs: gql(printSchema(schema)),
      resolvers: createResolversMap(schema),
    }),
    plugins,
    context: ({ req }) => {
      const context = {
        req,
        user: req.user, // `req.user` comes from `express-jwt`
      };
      return context;
    },
  });

...

The above mostly works, however when I'm attempting to add authorization to my project, using the @Authorization decorator / process from the type-graphql documentation, I'm hitting a road block: it doesn't seem like my authChecker is actually called.

I haven't dug too deep into the buildSchema function yet, I am wondering if I can somehow make this auth function available in the service container or something...

Anyway, hoping somebody might have an idea on how I can resolve this. If not, hopefully I'm able to find a workaround by stepping through buildSchema or something and I'll report back :). Thank you!

[MichalLytek]

gql(printSchema(schema)) for sure is loosing some features like @Extensions because they are not expressible in SDL.
However, I'm not sure why auth is not working for you as it's stored in the metadata storage

[MichalLytek]

Something different must be wrong with your setup. Middlewares should work normally.

[k-atama]

Thanks again for the reply - so far I haven't been able to track this down, so I'll switch to the non-federated version of the Apollo server to see if I have the same issue. If so, I guess the issue is pehraps something I've done on the config side (though I've stepped through the type-graphql logic on bootstrap and as far as I can tell things are "correct" in terms of how I've configured the custom auth.

One thing I'm not sure is "where" the authChecker within the schema after I run (type-graphql's buildSchema). E.g.

const schema = await buildSchema({
    resolvers,
    // register the 3rd party IOC container
    container: Container,
    authChecker: simpleAuthChecker,
  });

In other words, can I "see" the authChecker within the schema object above to confirm that at least this portion of the app is configured correctly?

[MichalLytek]

Just make the authChecker always return false so you will see that it's working. Or put console.log in the function body.

[k-atama]

I've certainly done that part - and unfortunately the console log isn't being hit :/ - this is why I think I have to go a bit deeper in the debugging.

As mentioned, type-graphql's checks for an authChecker on startup from buildSchema, and when I include the authChecker: simpleAuthChecker then the app starts up fine... it just seems to have no effect unfortunately (the console.log isn't hit, and the route isn't protected).

When you said "metadata storage", is this something I can see in the computed schema?

[MichalLytek]

You can log that in the global object, but metadata does not mean runtime schema, it's built from collected metadata