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
...

my frontend keeps attempting to refresh even though i just logged in

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 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?

Hi, can I set the expire duration for access and refresh token? I want to set a short time for dev demo purpose

Hi, when clicking on signout, or hitting any endpoint where we validate the session i get a inifinite loop of requests "try refresh token" cant figure out what's wrong

Hello, we are pretty new to SuperTokens and I am exploring its capabilities. We are trying to implement 2 ways of communication with SuperTokens. 1. Our frontend to our backend. (Should be fine) 2. Third party to our backend. Right now, I am trying to implement the 2nd one, I tried to use the emailpassword way to do it to test. Basically I created a signin function to send post request with the email and password to the Middleware, get the response and set up the cookies (access, front and refresh token), same for signout and signup. The problem I am having is that whenever the access token expired (refresh token is still alive), it won't generate new access token (even though I sent a request to the /auth/session/refresh). Another question is there a suggested way to implement third party to our backend communication authentication with SuperTokens?

Getting this error on Google login success. Though login is happening fine.

Error: No access, refresh token, API key or refresh handler callback is set.
    at OAuth2Client.getRequestMetadataAsync (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/google-auth-library/build/src/auth/oauth2client.js:272:19)
    at OAuth2Client.requestAsync (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/google-auth-library/build/src/auth/oauth2client.js:371:34)
    at OAuth2Client.request (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/google-auth-library/build/src/auth/oauth2client.js:365:25)
    at createAPIRequestAsync (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/googleapis-common/build/src/apirequest.js:273:31)
    at createAPIRequest (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/googleapis-common/build/src/apirequest.js:49:9)
    at Resource$Userinfo.get (/Users/hitesh/dev/jwt_supertokens_hasura/node_modules/googleapis/build/src/apis/oauth2/v2.js:104:58)
    at Object.<anonymous> (/Users/hitesh/dev/jwt_supertokens_hasura/dist/supertokens_config.js:117:57)
    at Generator.next (<anonymous>)
    at fulfilled (/Users/hitesh/dev/jwt_supertokens_hasura/dist/supertokens_config.js:5:58)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Any suggestions?

@rp_st did you train the chatbot on the discord data?

Heyy, We have a nest.js application deployed on Railway. In the frontend we have next.js deployed on Vercel. In the backend CORS is set like this

app.enableCors({
    origin: [
      '*',
      'http://localhost:3001',
      'http://localhost:3000',
      'https://*.vercel.app',
      'https://*.vercel.app/*',
    ],
    allowedHeaders: ['content-type', ...supertokens.getAllCORSHeaders()],
    credentials: true,
  });

But for all the vercel preview builds, we can't test the app because of CORS issues. Any Idea how to fix it.??