Hey! , i am trying to add the forgot-password functionality to my app , i was able to get it to send the mail but currently it sends it using the supertokens email, i want to configure it to use my mail I have added the below lines to supertokens init

emailDelivery: {
                    override: (originalImplementation) => {
                        return {
                            ...originalImplementation,
                            service: new EmailVerificationSMTPService({
                                smtpSettings,
                            }),
                            sendEmail: async function (input) {
                                if (input.type === 'PASSWORD_RESET') {
                                    // You can change the path, domain of the reset password link,
                                    // or even deep link it to your mobile app
...

Hi, got a little issue with our Android app on react native for a few days. it can log in and get an access token but when refreshing it logs us out this is what we changed before it started to happen : - "supertokens-node": "^8.5.0", + "supertokens-node": "^9.2.3", in the same deployment, we also set the cookieDomain to a wildcard to allow subdomains the weird thing is ios is fine

Has anyone successfully run supertokens core on heroku with heroku's psql? I'm getting an issue with drivers. The database url begins with

postgresql://

so it seems the

jdbc:

prefix is coming from someplace else?

Setting up PostgreSQL connection pool.
2022-10-07T02:04:20.842175+00:00 app[web.1]: Stopping SuperTokens...
2022-10-07T02:04:20.856938+00:00 app[web.1]: What caused the crash: Driver org.postgresql.Driver claims to not accept jdbcUrl, jdbc:postgres://ec2-107-23-76-12.compute-1.amazonaws.com:5432/....

Hi, I'm trying to setup passwordless auth (managed service), I've set up the managed core service but keep getting this error from the SuperToken API:

Error: 140438089361344:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

The service is running on a port locally and I've ensured to include

http://

and not

https://

in the

connectionURI

but that doesn't seem to fix the problem.

Hi! I am using Angular, and I replaced the HttpClient with fetch. My understanding is that Session.init() is supposed to add interceptors to fetch to send session data along with each http request. Is my understanding correct? If it is, then how can I debug to figure out why session data is not being sent when I make a fetch request?

invalid_grant with override on thirdparty

Hey @rp_st I want to get a list of all the users I have, but I want to do it from a script, not a server. I saw that there is a function in the node-supertoken lib but Im not able to use it (because I cannot use init()). I saw that there might be an endpoint in the CDI, but when I try to use GET im getting 404 not found in response. What is the right solution here? Thank you

Hi, I'm using multi tenants and wanted to share the session accros sub domains. So i referred here; https://supertokens.com/docs/emailpassword/common-customizations/sessions/share-sessions-across-sub-domains But the example there uses the prebuilt UI (

supertokens-auth-react

), and i'm using my custom UI (

supertokens-web-js

) How can i accomplish sharing session across domains with the custom UI? Thank you

I've got a super weird problem trying to implement Supertokens in a NextJS app for the first time. Using a NestJS backend and everything appears to be configured properly but when I try to sign up with Nest it hits my NestJS backend and then returns a 404. If I hit the exact same URL from the failed network request using CURL it works just fine eg:

http://localhost:3000/api/auth/signup/email/exists?email={email}

returns the expected result. If I visit the email exists URL directly in the browser it also prints the expected JSON. For some reason though the fetch that's getting triggered from the Next app always returns 404 🤔 Its not a CORS error... just a 404 as if the endpoint doesn't exist. I can log and see it hitting the supertokens middleware in all cases

getting this error in the console on the client side Access to fetch at 'https://api-development.bitcoinerfreelance.com/auth/session/refresh' from origin 'https://development.bitcoinerfreelance.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. Here is my Cors implementation on the back end app.use( cors({ origin: websiteDomain, allowedHeaders: ["content-type", ...supertokens.getAllCORSHeaders()], methods: ["GET", "PUT", "POST", "DELETE"], credentials: true, }) ); and my Supertokens init supertokens.init({ framework: "express", supertokens: { // TODO AARON - in production need to swap this with the connection for supertokens connectionURI: configData.superTokens.connectionURI, apiKey: configData.superTokens.apiKey, }, appInfo: { appName: "Bitcoiner Freelance", apiDomain: apiDomain, websiteDomain: websiteDomain, apiBasePath: "/auth", websiteBasePath: "/auth", },