I am Building a School management web app. My question is - Can i use one supertoken core for following things 1. Managing Normal User Login (already using third-party password less login) 2. Staff Role Based Login eg. Teachers, Developers, Support team etc. 3. Student login If yes can anyone share docs for the same.

Hey @Dheeraj Bhandari

No each one has seprate website. For staff login we have admin panel And for student login we have student website And for main website we have already implemented third-party password less login

Do each of these websites have their own backend? Or shared backend?

Have their own backend

right

So for each website i require seprate core ?

no. You can add new apps to an existing core

Ok sure

I have successful created multitenancy in a supertoken core. it shows me becoz it was created before now i have updated it. But when i am trying to see url to check is response is Hello its sshowing "Not Found" for example http://localhost:3567/appid-mycreatedApp

you need to append the

/hello

path to the URL

oh ok thanks

Can you enable backend debug logs and show the output when this api is called?

[18/11/2023] [INFO] Error: not Found at P:\Github\Hackwise\admin panel\server\src\index.ts:96:23 at Layer.handle_error (P:\Github\Hackwise\admin panel\server\node_modules\express\lib\router\layer.js:71:5) at trim_prefix (P:\Github\Hackwise\admin panel\server\node_modules\express\lib\router\index.js:326:13) at P:\Github\Hackwise\admin panel\server\node_modules\express\lib\router\index.js:286:9 at Function.process_params (P:\Github\Hackwise\admin panel\server\node_modules\express\lib\router\index.js:346:12) at next (P:\Github\Hackwise\admin panel\server\node_modules\express\lib\router\index.js:280:10) at P:\Github\Hackwise\admin panel\server\node_modules\supertokens-node\lib\build\framework\express\framework.js:197:24 at Generator.throw () at rejected (P:\Github\Hackwise\admin panel\server\node_modules\supertokens-node\lib\build\framework\express\framework.js:36:44) at processTicksAndRejections (node:internal/process/task_queues:95:5) [18/11/2023] [INFO] Incoming -> Method: [GET] - Url: [/auth/signup/email/exists?email=asddfas] - IP: [::1] - Status: [null]

Can you enabler backend debug logs for supertokens?

This is the backend logs when api called

as i said, please enable frontend and backend debug logs for supertokens and then show me

Not Able to Put debug log in backend

update to the latest backedn sdk

This is my superotken node version "supertokens-node": "^15.2.1",

and try again

ok let me try

you see a 500 error from the network call?

i am getting 404 Not found error

can i see the network tab?

hmm this is strange. The logs say that the requet is being handled, but you are seeing a 404

Express JS

is it hitting your app's error handler?

i have implemented supertoken in one of my other project with passwordless but in this new project i am getting issue

can i see the full error stack of the error that hits your error handler?

do other apis exposed by the backend sdk work?

No i just init the supertoken in backend Here it is // Super Token Init import supertokens from "supertokens-node"; import Session from "supertokens-node/recipe/session"; import EmailPassword from "supertokens-node/recipe/emailpassword"; import Dashboard from "supertokens-node/recipe/dashboard"; console.log(

${process.env.API_DOMAIN}

) console.log(

${process.env.WEBSITE_DOMAIN}

) supertokens.init({ framework: "express", supertokens: { connectionURI: process.env.SUPERTOKEN_CORE || "", apiKey: process.env.SUPERTOKEN_KEY || "", }, appInfo: { appName: "hackwiseAdmin", apiDomain:

${process.env.API_DOMAIN}

, websiteDomain:

${process.env.WEBSITE_DOMAIN}

, apiBasePath: "", websiteBasePath: "/" }, recipeList: [ EmailPassword.init(), // initializes signin / sign up features Session.init(), // initializes session features // Dashboard.init(), ] }); export default supertokens;

can you try calling the sign in API and seeing if that works?

same with signin api

hmm

whats the connection uri you have set on the backend for the supertokens core?

When i try with postman with sending json body it is showing { "message": "Missing input param: formFields" } but when i send correct body it return { "message": "not Found" }

whats the connectio uri you have set on the backend/

SUPERTOKEN_CORE = https://dev-c9ceff11141c11eeadfa979ba4fcdd1f-ap-southeast-1.aws.supertokens.io:3573/appid-hackwiseadmin

the value of

process.env.SUPERTOKEN_CORE

This one

right ok

yes

i see.

after all the routes

okay so for some reason, the core is saying not found

yes seems like

which version of the backend sdk are you on again?

i am using same core which i have used in my previous project i just created a new aap with in the core

can you navigate to the supertokens-node lib code in node_modules and add a

console.log(finalURL.toString())

right before this line? https://github.com/supertokens/supertokens-node/blob/15.2/lib/build/querier.js#L232 And then tell me what it prints out when you call the email exists API

ok doing

thanks

added but it is not printing in console

make sure that you have rebuilt the project and cleared cache, and restarted the backend server

i have changes current version supertoken from server and client to the version i have implemented in my previous project. Now everything is working fine

makes sense.

backend "supertokens-node": "^12.1.6", Client "supertokens-auth-react": "^0.28.1", "supertokens-web-js": "^0.3.0",

hmmm. It should have worked with the version we gave as well. Perhaps @sattvikc can help investigate

I am trying to reproducing this myself, will get back on this soon

"react": "^18.2.0",

not react. supertokens-auth-react

"supertokens-auth-react": "^0.35.1", "supertokens-web-js": "^0.8.0", This one Then i downgrade to "supertokens-auth-react": "^0.28.1", "supertokens-web-js": "^0.3.0", backend "supertokens-node": "^15.2.1", Then downgraded to "supertokens-node": "^12.1.6",

connectionURI

is same in both the cases ?

yes