https://supertokens.com/
Join Discord
hi, <@498057949541826571> thirdparty signinup POST request failes with response 404 on specific user...
# support-questions-legacy
b
hi, @rp_st thirdparty signinup POST request failes with response 404 on specific user. how can i debug this?
r
can you enable backend debug logs and show the output?
when this API is called
b
u mean supertokens log stored within /usr/lib/supertokens/logs?
r
backend sdk debug logs
see our troubleshooting section
b
2023-06-19T14:08:22.199Z com.supertokens {t: "2023-06-19T14:08:22.199Z", message: "middleware: Started", file: "/home/ubuntu/XXXXXXXX/node_modules/supertokens-node/lib/build/supertokens.js:225:26" sdkVer: "12.1.2"} 2023-06-19T14:08:22.199Z com.supertokens {t: "2023-06-19T14:08:22.199Z", message: "middleware: requestRID is: thirdpartyemailpassword", file: "/home/ubuntu/XXXXXXXX/node_modules/supertokens-node/lib/build/supertokens.js:239:26" sdkVer: "12.1.2"} 2023-06-19T14:08:22.201Z com.supertokens {t: "2023-06-19T14:08:22.200Z", message: "middleware: Checking recipe ID for match: thirdpartyemailpassword", file: "/home/ubuntu/XXXXXXXX/node_modules/supertokens-node/lib/build/supertokens.js:248:34" sdkVer: "12.1.2"} 2023-06-19T14:08:22.202Z com.supertokens {t: "2023-06-19T14:08:22.202Z", message: "middleware: Matched with recipe ID: thirdpartyemailpassword", file: "/home/ubuntu/XXXXXXXX/node_modules/supertokens-node/lib/build/supertokens.js:261:30" sdkVer: "12.1.2"} 2023-06-19T14:08:22.202Z com.supertokens {t: "2023-06-19T14:08:22.202Z", message: "middleware: Request being handled by recipe. ID is: /signinup", file: "/home/ubuntu/XXXXXXXX/node_modules/supertokens-node/lib/build/supertokens.js:273:30" sdkVer: "12.1.2"} 2023-06-19T14:08:22.369Z com.supertokens {t: "2023-06-19T14:08:22.369Z", message: "errorHandler: Started", file: "/home/ubuntu/XXXXXXXX/node_modules/supertokens-node/lib/build/supertokens.js:316:26" sdkVer: "12.1.2"} 2023-06-19T14:08:22.370Z com.supertokens {t: "2023-06-19T14:08:22.370Z", message: "errorHandler: Started", file: "/home/ubuntu/XXXXXXXX/node_modules/supertokens-node/lib/build/supertokens.js:316:26" sdkVer: "12.1.2"}
hi, @rp_st , here is the log.
Hi, @rp_st so I digged a bit and found that it is about some customization for account deduplication and google third party user id changing after deleting and reactivating google workspace email. my question is - is supertokens handling this case where thirdparty user id changes while email stays the same correctly?
r
third party user IDs changing means that it's a different provider.
so that will be treated as a different user.
b
not different provider. same google, same email but different thirdparty user id.
it happens when u delete workspace email and create again with same address.
r
ahh right. Well, that would require account linking as a feature on our end. Which we don't have yet.
You could delete the older user in the system and then sign up the new one again though
b
is there any way to create user with specific user id?
r
yea. See the user ID mapping feature in the migration section
b
this error happens sometimes on backend. where is this from and how can i fix this?
message
9 Views
PreviousNext
Powered by

SuperTokens.com

SuperTokens is an open source authentication solution offering features like: Different types of login: Email / password, Passwordless (OTP or Magic link based).

Powered by