What add request.login in nestjs

Question

I have passport local guard:

export class LocalGuard extends AuthGuard('local') {
  async canActivate(context: ExecutionContext): Promise {
    const result = (await super.canActivate(context)) as boolean;
    await super.logIn(context.switchToHttp().getRequest());
    return result;
  }
}

And I implemented guard for google auth like:

export class GoogleAuthGuard implements CanActivate {
  canActivate(
    context: ExecutionContext,
  ){
    const req = context.switchToHttp().getRequest();
    // get access token from request...
    const user = // validate against google api 
    request.login(user, (err) => {});

    return true;
  }
}

I implemented guard with direct calls to google api to validate access token as I see that passport doesn't have something similar to just authenticate access token.
With request.login() express-session is created and stored in redis it's all fine.

I just don't understand from where this request.login() is coming?

What adds it, passport (I don't use it in this guard), nestjs or session-express.

user_9576186 · Answer

passport is what is adding the login() method to the request object. Regardless if you use it in the guard or not, the request object has still been modified by passport, so it has this login method. It's used for creating a session with your session store of choice. I've got a decent write-up of the integration between Nest, passport, and how to create a session based authentication system on dev.to that may help shed some light on what's going on under the hood with NestJS and passport.

What add request.login in nestjs

1 Answers