hi! how can i prevent

SignInUp

component from

supertokens-auth-react/recipe/passwordless

redirecting to

/auth

i am overriding it to only confirm

OTP

by creating

verify-phone

route, and adding this to frontend config

signInUpFeature: { disableDefaultUI: true }

Hello This seems like an awesome project. I currently have my users in my mongoDB and logins in google identity management. In the future it would be cool to have everything in mongodb (when the adapter is implemented). My backend is built with c# in asp core. I dont see any mentions of dot net / asp core / c# in the guides or in this discord. Will it be supported or am i the only one who have requested it ?

My session keeps expiring I tried adding the frontend SDK to all of my pages but it doesn't seem to work

i want to use supertokens_python with websockets in fastapi. is there a verify_session that works for a websocket route?

https://discord.com/channels/603466164219281420/907932061669654548/1202007865028775937 I've started the migration from the Remix example to the Next.js app directory example. (At least for now.) And I think Remix does things way better. 😅 I wanted to suggest adding documentation on how to use the

ThirdPartyEmailPassword

option without using the Express middleware, and perhaps suggest exposing clear functions for it if they aren't yet available. (I assumed that they would be available since we now have things like

*withoutRequestResponse()

.) I've been approached multiple times on both my Remix and my SvelteKit examples regarding how to get

ThirdPartyEmailPassword

up and running. It seems to be the most common recipe (or one of the most common). And having a way to set things up clearly (without having to bring other SuperTokens packages into the mix) would likely be a big win. It might also alleviate some of the package management that SuperTokens has to deal with for various JS frameworks. I would look into it, but I unfortunately haven't had the time to scrutinize SuperTokens's internals like I did last time. 😅 I'm still looking for an opportunity. I'm only just now getting to the Next.js app dir example. (I know SuperTokens has one. This would just be one that would be more direct -- requiring less NPM packages and higher order functions.)

We are trying to host our system on GCP. We are using email password recipe and we want to use cloudrun. Just need some pointers on resources that will help to do this or if it is even possible. Thanks!

Good morning. Is there anyway to get the user password hashes from ST's API?

Guys I am facing an issue while fetching a user through email. The auth dashboard shows the user is signedUp and Auth method under Email password. If there is any other method to go through forgot password flow. In the current flow from frontend it sends a token, so it does not verify if a user is already present in the database. It just sends out the email to whatever email you provide. Frontend is used for thirdparty Following is config file import ThirdPartyEmailPassword from "supertokens-node/recipe/thirdpartyemailpassword"; export function getApiDomain() { const apiPort = process.env.REACT_APP_API_PORT || 4001; const apiUrl = process.env.REACT_APP_API_URL || `http://localhost:${apiPort}`; return apiUrl; } export function getWebsiteDomain() { const websitePort = process.env.REACT_APP_WEBSITE_PORT || 3000; const websiteUrl = process.env.REACT_APP_WEBSITE_URL || `http://localhost:${websitePort}`; return websiteUrl; } export const SuperTokensConfig: TypeInput = { supertokens: { connectionURI: "localhost:3567", }, appInfo: { appName: "Auth Middleware Express", apiDomain: getApiDomain(), websiteDomain: getWebsiteDomain(), }, recipeList: [ ThirdPartyEmailPassword.init({ providers: [ // Google({ // clientId:"ID", // clientSecret: "SECRET", // }), ], }), Session.init({}), Dashboard.init(), UserMetadata.init(), ], }; Following is my controller file import { getUsersByEmail } from "supertokens-node/recipe/thirdpartyemailpassword"; export const createTokenForResetPassword = async (req: any, res: any) => { const { email } = req.body; try { const getUser = await getUserByEmail(email); console.log("EMAIL ", email); console.log("USER ",getUser); // const createVeriToken = await createResetPasswordToken(getUser.userId); res.send({ status: "OK" }); } catch (err) { res.status(500) } };

Hi @rp_st & @nkshah2 , We are using supertoken web js version no - 0.8.0 and below are our domain and api url. Cookie Name - .xyz.co.in API URL Name - https://abc.xyz.co.in However we are facing the issue where the cookie domain is created SAccessToken with domain https://abc.xyz.co.in. We really dont know how exactly this is happening as entire cookie management is done by SuperToken. Would really appreciate if you can help us?

Hello, I need a bit of clarification on pricing. So I'm using self hosted core in react + react native + nestjs stack, but I'm a bit confused with multitenancy price calculation. If I get this correct, I have 0 tenants, as I don't really need this feature and started working with library before it was released, will this feature take affect on my project or I can skip this at all in my case?