Hey!

You can use the auth guard as the docs says and pass the sessionRequired boolean as false in it. This way, you can then check if the ctx.session object is defined in the api logic and if it’s not defined, the user is not logged in.

(in an few hours)

Anyway, adding a builder like this to your project should be fairly straightforward, but it's not something we provide out of the box. If this is a built-in in, maybe there is a way to make it work, but I don't see it in NestJs docs. if you could point me to the right docs I can check.

anyway

It looks like the

can

and

cannot

calls should not interface with our library

so you can use this syntax, it should not be a problem

also, we provide a similar functionality: https://supertokens.com/docs/emailpassword/user-roles/protecting-routes

It's not as well integrated with nestjs, but this is also a possibility