We just don't have a django example in the repo yet - feel free to contribute it

Oh my bad! Man you guys are on top of it. I’ll see what I can do.

Didn't even come across this in my searches ahaha - that's extremely helpful - back when I was originally doing it - it took me a little while to realise in the call to signin or signinup had the Set-Cookie header, and I was going crazy looking for a 'login' function to call with the Username & Password/etc (because I saw the sign out function) bahaha.

Oh - that's weird - google doesn't seem to have the blog indexed?

That'd be why I never found it haha :P

Actually - I'm wrong (site:https://supertokens.com/blog/) shows results - but google seems to be doing some weird indexing - as I can't get that specific page/documentation to come up with a google search, and it seems to index the categories higher for some reason?

hmmm. Will investigate this.

Maybe just stick a link somewhere in the docs to the page - as it'll clear up confusion for a fair few people im guessing? Google can play catch up later :P

Hmm. Can do. Will think about it.

should be pages/api/user

Can you make a PR for this please?

Can't be bothered rn. Btw, how do I get the current logged in user's data in Next.js? And is it possible to extend this object with more data?

made this change on our test site. Will push it to prod soon... thanks

i j

Hello. I am new to supertokens. I am using nest js with supertokens. As documentation auth.module has static function

static forRoot({ connectionURI, apiKey, appInfo }: AuthModuleConfig): DynamicModule {
      return {
        providers: [
          {
            useValue: {
              appInfo,
              connectionURI,
              apiKey,
            },
            provide: ConfigInjectionToken,
          },
        ],
        exports: [],
        imports: [],
        module: AuthModule,
      };
    }

And Then I have used this method to to app.module something like this

imports: [
    AuthModule.forRoot({
      connectionURI: process.env.AUTH_CONNECTION_URI,
      appInfo: {
        appName: "canopy",
        apiDomain: process.env.API_DOMAIN,
        websiteDomain: process.env.WEBSITE_DOMAIN,
        apiBasePath: "/auth/",
        websiteBasePath: "/",
      },
    }),
    ConfigModule.forRoot({
      isGlobal: true,
      load: [config],
    })
  ],

My question is how can i use configService to get the env values in AuthModule.forRoot function ?

@User can help out with this.

Hi @User, what

configService

are you referring to?

If you want to access those values in another service you can take a look at

supertokens.service.ts

. I don't think we have/use a config service.

Something like this

@Injectable()
export class YourService {
    constructor(@Inject(ConfigInjectionToken) private config: AuthModuleConfig) {
    }
}

Thanks @User for the quick response.

configService

in nest js helps to get the env vars when injected. Somethig like this in app.module.ts

TypeOrmModule.forRootAsync({
      useFactory:async (config: ConfigService) => ({
        type: 'postgres',
        host: config.get('POSTGRES_HOST'),
        port: config.get('POSTGRES_PORT'),
        username: config.get('POSTGRES_USER'),
        password: config.get('POSTGRES_PASSWORD'),
        database: config.get('POSTGRES_DATABASE'),
      }),
      inject: [ConfigService]
    })

I want to do something similar to AuthModule as well

oh I see, just a few mins, I'll set something up locally

Sure. Thanks again.

basically instead of

useValue

you should have the

useFactory

and

inject

in the

forRoot

of auth.module

@User I am sorry but I didn't get you here. but using

useFactory

How will i get appInfo, connectionURI, apiKey, these values. I am new here so please don't mind for my silly questions

No silly questions 🙂 I'll copy an example here in a sec, that was intended as a very highlevel/quick summary of what I'm doing.

You could do something like this:

ts
import {
    MiddlewareConsumer,
    Module,
    NestModule,
    DynamicModule,
    FactoryProvider,
    ModuleMetadata,
  } from '@nestjs/common';
  
import { ConfigInjectionToken, AuthModuleConfig } from './config.interface';
  
type ModuleRootConf = Omit<FactoryProvider<AuthModuleConfig>, "provide" | "scope"> & Pick<ModuleMetadata, 'imports'>;

  @Module({
    providers: [],
    exports: [],
    controllers: [],
  })
  export class AuthModule implements NestModule {
    configure(consumer: MiddlewareConsumer) {
    }
  
    static forRoot({ useFactory, inject, imports }: ModuleRootConf): DynamicModule {
      return {
        providers: [
          {
            useFactory,
            inject,
            provide: ConfigInjectionToken,
          },
        ],
        imports,
        exports: [],
        module: AuthModule,
      };
    }
  }

oh one thing I skipped is adding middleware in

configure

, you should do that I just didn't have the full setup locally 😄

the main thing is the new

forRoot

interface. maybe it'd be better renamed to

forRootAsync

@User Sorry again. It worked Thanks alot. But can you give me an idea what this line is doing

type ModuleRootConf = Omit<FactoryProvider<AuthModuleConfig>, "provide" | "scope"> & Pick<ModuleMetadata, 'imports'>;

Sure. It's a bit convoluted 😄