[BUG] Middleware not called while using nestjs-session with @nestjs/graphql

What is the current behavior?

I don’t succeed to make this package work with @nestjs/graphql. When I call a REST route, it’s working well, and the session(req, res, next) middleware (from express-session) is well called. But when I call the GraphQL entrypoint, the middleware is not called at all.

I’ve digged deep in nestjs source-code, but I don’t know really where to look.

Even with a forRoutes: [{ path: '/*', method: RequestMethod.ALL }], this change nothing.

What is the expected behavior?

In practice, the consequences are that no cookie is defined in the GraphQL response, and so, the sessions don’t work.

Please mention other relevant information such as Node.js version and Operating System.

[clayrisser]

I’m using redis to manage the session. It’s really odd because the session in my controllers works great. However, with graphql, every request creates a brand new empty session.

Session in Controllers

Session in Graphql

Notice that only the first session is used in the controller, but all the rest of the sessions are created new with every graphql request.

[Nabellaleen]

So, I’ve built a simple module to do the init and session, and it works well. So I think the problem is not from your side, but from @nestjs/passport side who should integrate a way to register these middlewares.

import {
    createModule,
    FacadeModuleStaticOptional
  } from 'create-nestjs-middleware-module';
import * as passport from 'passport';

interface Options {
    maxDuration?: number
}

export const PassportSessionModule = createModule<Options>(options => {
    return [
        passport.initialize(),
        passport.session(),
    ]
    // app.use(passport.initialize());
    // app.use(passport.session());
}) as FacadeModuleStaticOptional<Options>