hi there, I have an issue with my tenant...not sur...
# support-questions-legacyc
cruaier
11/14/2023, 3:43 PMhi there, I have an issue with my tenant...not sure what might cause it:
Error: SuperTokens core threw an error for a POST request to path: '/692da2df-dca9-48aa-8556-9be2a082fa7f/recipe/user/password/reset/token/consume' with status code: 400 and message: AppId or tenantId not found => Tenant with the following connectionURIDomain, appId and tenantId combination not found:
the error only happens when trying to reset a users password, all other auth functions seem to work
cruaier
11/14/2023, 3:50 PMchecking into the database (using the managed service), I can see that the app_id in the table tenants is "public" - is that correct?
cruaier
11/14/2023, 3:55 PMlooking further, I can see that the log shows a tenantId which is a uuid, not "public" - what probably causes the error...but where's the uuid coming from?
r
rp_st
11/14/2023, 4:06 PMyea, the UUID is causing the error. It's coming cause the the during password reset link creation, you are somehow passing this UUID as the tenant ID to the backend
rp_st
11/14/2023, 4:07 PMso you need to see how that could be happening from your frontend
rp_st
11/14/2023, 4:07 PMare you using the multi tenancy recipe at all?
cruaier
11/15/2023, 6:22 AMfrontend is using the function:
import { submitNewPassword } from 'supertokens-web-js/recipe/thirdpartyemailpassword';
r
rp_st
11/15/2023, 6:38 AMwhy do you have the UUID as part of the path?
rp_st
11/15/2023, 6:38 AMthats causing this issue
c
cruaier
11/15/2023, 8:24 AMhmm understandable, but that's the supertokens lib generating it, right?
cruaier
11/15/2023, 8:24 AMI'll check later on what is happening there
r
rp_st
11/15/2023, 8:50 AMno. We don't add a UUID, unless you return that value from the multiteneancy.init -> getTenantId function (from the frontend).
c
cruaier
11/15/2023, 8:54 AMwhen I remove the uuid from the request I get the error:
{
"status": "RESET_PASSWORD_INVALID_TOKEN_ERROR"
}
cruaier
11/15/2023, 8:57 AMthe init on the frontend is very minimalistic:
SuperTokens.init({
appInfo: {
appName: 'XXX',
apiDomain: 'XXX',
},
recipeList: [ThirdPartyEmailPassword.init(), Session.init({ tokenTransferMethod: 'header' })],
});
r
rp_st
11/15/2023, 9:33 AMAre you manually making the api call? Can I see how you are doing that?
c
cruaier
11/15/2023, 9:43 AMthe one without uid was done with postman yes
cruaier
11/15/2023, 9:51 AMcruaier
11/15/2023, 9:51 AMthe only header I set was Rid with thirdpartyemailpassword
r
rp_st
11/15/2023, 10:03 AMthen you must be passing a bad value for the token. Also, the token is one time use
rp_st
11/15/2023, 10:03 AMthe image you sent doesn't load
c
cruaier
11/15/2023, 10:22 AMI'll check again tmr.. I don't why the frontend is generating this kind of url in the first place though
r
rp_st
11/15/2023, 10:22 AMyeaa.. very strange
c
cruaier
11/15/2023, 10:36 AMI found the culprit:
await ThirdPartyEmailPassword.sendResetPasswordEmail(
'public',
user.id,
email,
);
cruaier
11/15/2023, 10:36 AMthe code should sent out invitation emails...but the user.id as 2nd param is wrong
r
rp_st
11/15/2023, 10:38 AMIt seems correct from the function signature in our SDK
rp_st
11/15/2023, 10:39 AMAhh. Its a bug in our backend SDK
rp_st
11/15/2023, 10:41 AMWe will release a fix today
c
cruaier
11/15/2023, 11:08 AMok great
r
rp_st
11/15/2023, 12:14 PMhey @cruaier we have released the fix in our latest node SDK. Please try it out.
c
cruaier
11/15/2023, 1:05 PMOK, will check it out and report
r
rp_st
11/15/2023, 1:56 PMthanks
c
cruaier
11/16/2023, 4:38 AMI can confirm, it works now correctly - thanks for the fix
r
rp_st
11/16/2023, 6:36 AMthanks!
27 Views