Nest: JWT: How to access it after using UseGuards?

[maxime1992]

I'm submitting a...

[ ] Regression 
[ ] Bug report
[ ] Feature request
[ x ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

I have no idea how to access a JWT token and it's missing in doc/github example.

Let's take this one: https://github.com/nestjs/nest/blob/master/sample/19-auth/src/auth/auth.controller.ts#L16

Here, we're securing the route:

  @Get('data')
  @UseGuards(AuthGuard('jwt'))
  findAll() {
    // this route is restricted
  }

But how can we have access to the current JWT (to retrieve user id or email for example).

Environment

Nest version: 5.0.0

For Tooling issues:
- Node version: 8.9.4
- Platform:  Linux

[adrien2p]

If you don’t pass any options to auth guard, you should have access to the user by calling req.user

[maxime1992]

Oh it's done automagically, no need to do that ourselves! Cool, thanks @adrien2p.

[zhmushan]

@maxime1992
Hi, can you help me give an example of how to configure, I have been confused for a long time here

[maxime1992]

Sure thing. I've made a demo app and you should be able to find what you need in there:

https://gitlab.com/maxime1992/emails-app/blob/master/backend/src/emails/emails.controller.ts

Let me know if you need more help but I think you should manage to find what you want with that project :)

[zhmushan]

Thanks @maxime1992 .
Everything suddenly understood, after seeing export const Usr = createParamDecorator((data,req)=> req.user);
This is a huge help for me, thanks again.

[cloakedch]

I think this should go in the docs. Was looking for the same.
Plain AuthGuard without being able to use the token for further verification (chained guards) is pretty useless.

This post helped me a lot.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.