There is one more thing, in the frontend if I stay...
# generalh
hehohesda_12345
06/20/2023, 11:50 AMThere is one more thing, in the frontend if I stayed idle for some time (couple of seconds), after certain amount of time my API will throw error UNKNOWN_USER_ID, on verifySession().
By staying idle I mean, not sending any req to backend.
Does this happen because access token validity is 60 second by default and I am not handling expiration of access tokens?
r
rp_st
06/20/2023, 11:56 AMhey @hehohesda_12345 are you using email verification recipe in required mode on the backend?
h
hehohesda_12345
06/20/2023, 3:04 PMYes I am using that.
I am using ThirdPartyEmailPassword, but I am only utilizing third party providers only(google) for now.
hehohesda_12345
06/20/2023, 3:04 PMsupertokens.init({
framework: "express",
supertokens: {
connectionURI: process.env.SUPERTOKENS_CORE_CONNECTION_URI,
apiKey: process.env.SUPERTOKENS_CORE_API_KEY,
},
appInfo: {
appName: "",
apiDomain: process.env.API_DOMAIN,
websiteDomain: process.env.CLIENT_ORIGIN_URL,
apiBasePath: "/api/auth",
websiteBasePath: "/auth",
},
recipeList: [
ThirdPartyEmailPassword.init({}),
Emailverification.init({
mode: "REQUIRED",
}),
Session.init(),
],
});
This is the config in API
r
rp_st
06/20/2023, 4:44 PMright. And the session is being created for a user that does not exist in supertokens?
h
hehohesda_12345
06/22/2023, 11:22 AMNo, That never happened with me.
Any ways I have set it to optional mode and now its working fine.
Also I wanted to know if I am only utilizing social logins in ThirdPartyEmailPassword, everything will work fine? I my implment my own login password in the future so I am using this recipe for now.
r
rp_st
06/22/2023, 12:23 PMYes. You should just disable the email password related APIs
h
hehohesda_12345
06/23/2023, 6:32 AMThank you