So after some reading and looking into it.
I've been using the guard for the whole app instead of for each route. SInce I was using it that way it was trying to do DI on it, and it didn't work.
If I did
@UseGuard(new AuthGuard())
it would work.
.auha
01/11/2024, 9:06 PM
@porcellus Do you know how to make the settings for ConfigInjectionToken more persistent? After doing a forRoot with the dynamic module I am not able to use the
SupertokensService
any other module because the DI does not know how to inject
ConfigInjectionToken
config. Do you know how to get that to work?
p
porcellus
01/15/2024, 8:55 AM
I can look into this a bit more to provide an exact code snippet, but I think you just need to move the provider for
ConfigInjectionToken
to a place where other modules can use it (or possibly set it as an export) not sure, I haven't worked in Nest for a while
SuperTokens is an open source authentication solution offering features like: Different types of login: Email / password, Passwordless (OTP or Magic link based).