I'm trying to self-host Supertokens Core, but it only works if I run it as administrator on Windows. I'm trying to start it when I start my server via npm's package.json, so I would prefer not to have to run my whole project as admin. How can I make sure that supertokens runs as admin on Windows and sudo on Linux? I've looked at

sudo-prompt

, but I'm not sure how to call it from a npm script like I can call

tsc

,

eslint

,

cross-env

, or

ts-node-dev

.

Hello, I am trying to break my overrides out to be more modular, but I am having trouble typing them.

ts
import { db } from '@db/index';
import { users, profiles } from '@db/schema';

const thirdPartySignInUpOverride =
  (originalImplementation) => async (input) => {
    let response = await originalImplementation.thirdPartySignInUp(input);

    if (response.status === 'OK') {
      let { id, emails } = response.user;
      console.log('USER SIGNED UP', id);
      await db.transaction(async (trx) => {
        await trx.insert(users).values({
          id,
          email: emails[0],
        });
        await trx.insert(profiles).values({
          userId: id,
        });
      });

      // This is the response from the OAuth 2 provider that contains their tokens or user info.
      let providerAccessToken = response.oAuthTokens['access_token'];
      let firstName =
        response.rawUserInfoFromProvider.fromUserInfoAPI!['first_name'];

      if (
        response.createdNewRecipeUser &&
        response.user.loginMethods.length === 1
      ) {
        // TODO: Post sign up logic
      } else {
        // TODO: Post sign in logic
      }
    }
    return response;
  };

export default thirdPartySignInUpOverride;

I am really not sure of what the

originalImplementation

type should be. I have tried creating an interface from ThirdPartyPasswordless recipe, but that didn't work at all. Any ideas? Edit: Found a way to type using RecipeInterface. Not sure if this is documented? I had to search in discord and got lucky

Hi there! Users metadata update stopped working a while ago so I'm wondering if we're doing things right. Here is our current flow: 1. Login is done on the client side (with the netlify recipe) 2. A user can update a specific metadata. We have a route that calls

updateUserMetadata

, this works 3. Then client-side, we try to refresh the metadata and it does not work:

ts
  const attemptRefreshingSession = await Session.attemptRefreshingSession();
  const sessionExists = await Session.doesSessionExist();
  if (sessionExists) {
    const user_id = await Session.getUserId();
    const accessTokenPayload = await Session.getAccessTokenPayloadSecurely();

accessTokenPayload

contains the same metadata as before. User needs to logout and login again to see the refreshed metadata. What should we do?

json
    "supertokens-node": "^13.1.5",
    "supertokens-web-js": "^0.5.0",

Hi, I need your help, is there a way in supertoken for Google-One-Tap, for social login?

Getting the following error when trying to send a verification e-mail:

[INFO] 05:38:57 ts-node-dev ver. 2.0.0 (using ts-node ver. 10.9.2, typescript ver. 4.9.5)
API Server listening on port 3001
Error: 140384285034368:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

where my smtp settings are:

ts
let smtpSettings = {
    host: "mail.privateemail.com",
    authUsername: "no-reply@website.com",
    password: "password",
    port: 587,
    from: {
        name: "Website No Reply",
        email: "no-reply@website.com"
    },
    secure: true
}

Tried switching to port 465 as well but that times out the connection w/ a 504 error and has the following server side error after 2 minutes:

Error: Connection timeout
    at SMTPConnection._formatError (/app/node_modules/nodemailer/lib/smtp-connection/index.js:790:19)
    at SMTPConnection._onError (/app/node_modules/nodemailer/lib/smtp-connection/index.js:776:20)
    at Timeout.<anonymous> (/app/node_modules/nodemailer/lib/smtp-connection/index.js:235:22)
    at listOnTimeout (internal/timers.js:557:17)
    at processTimers (internal/timers.js:500:7)

I tried testing it in java like so and this does work: Ran some [tests]() on . so not sure what I'm doing entirely wrong on the NodeJS back end not sure if relevant at all but I am using NameCheap's mail service (

privateemail.com

) with the DNS handled through Cloudflare. Followed the instructions Namecheap provides [here]() & [here]() Hope that's everything you might need to assist me with my issue

Hi I'm trying to use custom form fields in Angular/Node.js.. I keep getting: "Are you sending too many / too few formFields?" I have the form fields setup on backend but frontend with Angular not really working

Is there any documentation on best practices when self-hosting SuperTokens Core? I was thinking if it is feasible to run the core on a Cloud Run service instance. Thoughts?

Trying to get an SMS API key for our self hosted service, but I can't find the pricing for SMS alone or create the 'development' or 'production' envs as described here https://supertokens.com/docs/passwordless/sms-delivery/supertokens-sms-service#1-get-the-sms-api-key Does these apply to self hosted instances? And is it possible to get an SMS api key for self hosted instances?

We are experiencing high latency while calling createCode and consumeUser? Together they are consuming around 28s.

You may be familiar of the server actions in nextjs. How do I protect the server actions for authorized usage ? We can protect the api with "withSession" helper function but as we dont have any request in server actions so I can use that func.