https://supertokens.com/
Join Discord
Hello. I've been using the ThirdPartyEmailPassword recipe for my Supertokens setup on the backend an...
# support-questions-legacy
n
Hello. I've been using the ThirdPartyEmailPassword recipe for my Supertokens setup on the backend and everything worked great. Now I actually wanted to switch to ThirdParty recipe, since I'm not really doing email password login currently in my app. But after switching the backend config to use ThirdParty recipe, the 
/{apiBasePath}/signinup
route is no longer there and I can not POST to it. Can anyone suggest what could be the cause? Thanks.
r
hey @nicktgn have you switched to third party recipe on the frontend and backend?
n
my frontend is C# so its totally custom, doesn't use any recipes 😅
r
right.
you are getting a 404 on the backend?
n
500
r
any error stack?
n
nope
r
Either from the core or from our backend sdk
maybe you want to add a global error handler and see what the error is
(on the backend)
n
/signinup
is now seem to be just hitting my Go router (fiber)
and fiber currently reports 500 when there is no route
r
ok
so, what rid are you passing in the request header?
n
oh
yea, still passing the old one
thirdpartyemailpassword
So backend SDK is processing requests based on this rid header?
r
yup
thats how it does recipe routing
so change that to thirdparty
n
I see... yep, got it.
Fairly obscure detail, very easy to miss 😅
r
agreed.
We will be streamllining these recipes - ideally just removing the combination ones.
But in a few months..
should make stuff easier
n
That sounds great!
Looking forward to it.
Alright. Thanks again for your help! You saved me hours of banging my head against the wall 😅
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