@User the routes exposed via the middleware are defined here: https://app.swaggerhub.com/apis/supertokens/FDI

Depending on which recipes you initialise, those routes will be exposed.

Thank you very much, haven't found the FDI spec url in the docs.

Wow, i see it now.

🙈

haha.. fair enough

what's the reason you want to which APIs it exposes? Cause you want to call them manually? Or just curiosity?

Just out of curiosity

Fair enough.

So, i ran into a "problem". I want to implement a post signup callback on NestJS to add create the user in my own database and assign roles to them. But the way i need to initialize supertokens in a static method context don't allow for injecting the database service. Do you have any thoughts about this? (Implementation i followed: https://supertokens.io/docs/emailpassword/nestjs/guide)

@User - can you please help out with this question?

I'm just checking, but I think there should be a way to do this in a kind of "lazy loaded" way.

Well, the best thing I could come up with now is to add a service into the Auth module. This service could handle initializing the SDK and have access to injected stuff

@User if this works, perhaps we should change the docs to reflect this way of initialising as opposed to the static way?

yeah, sure. it adds an extra step but this seems to be a common enough usecase.

I'll do it over the weekend if that's ok, but I'm happy to help if you need it sooner.

@User does this help for now? Or would you like an example of how it can be done?

Yes, thanks for the advice. It think that will solve it. Will let a snippet here if it's implemented, so you can use it in the docs

While this works like a charm now. I ran into another hurdle. I disabled the signup by overriding the

signUpPOST

api because i want to add users manually as an admin. But the

supertokens-node

sdk doesn't provide me with a method to get the current recipe and e.g. call

signInPOST

on it.

You can't call the API itself, but you can create a new session by calling createNewSession (https://supertokens.io/docs/session/common-customizations/sessions/new-session).

If you are calling the originalImplementation method in your override, that should already have called the createNewSession function

Why would you want to call signInPost inside signUpPost anyway?

I just want to call the signUp function out of band (from somewhere else in the backend). I dont want users to create accounts themselves.

So with the override disable the signup functionality and so the route in the API.

Maybe there is a better way to just let "me" as an admin or the backend itself create users but don't publish a route where users can signup. Signin etc should work as normal

Yes. That’s possible. Give me 15-20 mins. Will get back

I think you are looking for this: https://supertokens.io/docs/nodejs/emailpassword/signup

Yes, the problem i can't get access to the instance of the

Emailpassword

recipe that owns that function.

It's a singleton, so if you import the recipe it has this as a static method that will call this on the right instance

Yeah, i see now. Thought i had checked that already.. Sorry for wasting your time!