Hello I'm trying to login/signup using thirdpartyp...
# support-questions-legacyk
khaledfromvee_63013
11/21/2023, 2:25 PMHello I'm trying to login/signup using thirdpartypasswordless, i get the below error from supertokens core when trying to connect using facebook in our dev env, but its working fine in staging and production, any ideas?
Copy code
Error: SuperTokens core threw an error for a GET request to path: '/session/recipe/multitenancy/tenant' with status code: 400 and message: AppId or tenantId not found => Tenant with the following connectionURIDomain, appId and tenantId combination not found: (st-dev-a656a980-31d0-11ee-b7de-49557aa25a13.aws.supertokens.io, public, session)
at Querier.sendRequestHelper (/app/node_modules/supertokens-node/lib/build/querier.js:361:27)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Querier.sendGetRequest (/app/node_modules/supertokens-node/lib/build/querier.js:173:40)
at async Object.getTenant (/app/node_modules/supertokens-node/lib/build/recipe/multitenancy/recipeImplementation.js:34:28)
at async Object.getProvider (/app/node_modules/supertokens-node/lib/build/recipe/thirdparty/recipeImplementation.js:108:34)
at async Object.getProvider (/app/node_modules/supertokens-node/lib/build/recipe/thirdpartypasswordless/recipeImplementation/thirdPartyRecipeImplementation.js:24:20)
at async Object.authorisationUrlAPI [as default] (/app/node_modules/supertokens-node/lib/build/recipe/thirdparty/api/authorisationUrl.js:43:30)
at async Recipe.handleAPIRequest (/app/node_modules/supertokens-node/lib/build/recipe/thirdparty/recipe.js:75:24)
at async Recipe.handleAPIRequest (/app/node_modules/supertokens-node/lib/build/recipe/thirdpartypasswordless/recipe.js:64:24)
at async SuperTokens.middleware (/app/node_modules/supertokens-node/lib/build/supertokens.js:195:38)r
rp_st
11/21/2023, 2:25 PMHey @khaledfromvee_63013
rp_st
11/21/2023, 2:26 PMYou are somehow passing the tenant id as “session”
rp_st
11/21/2023, 2:26 PMSo you might want to see from where that’s coming into the picture.
k
khaledfromvee_63013
11/21/2023, 2:33 PMyes i saw that, our dev and staging have different clusters but they share same exact code
khaledfromvee_63013
11/21/2023, 2:34 PMwhere do think this issue is coming from, the backend or frontend?
khaledfromvee_63013
11/21/2023, 2:34 PMstaging is working fine
r
rp_st
11/21/2023, 2:34 PMmost likely the frontend cause thats what defines the tenant ID
rp_st
11/21/2023, 2:34 PMit could also just be that you have not created the tenant with the required ID (in this case "session") in the core.
i
idanto
11/21/2023, 3:06 PMthanks @rp_st it was some endpoint mapping that has changed in our gateway that mapped the url to auth/session/authorisationurl intead of just /auth/authorisationurl it some how effected the request to the core
r
rp_st
11/21/2023, 3:15 PMright! okay
3 Views