/bin/sh: 1: java: not found

ubuntu how to install java and which version ? iam now working node test running but this problem cc: @rp_st

is there a way to list all users?

How do the

supertokens-node

verifySession

and

Session.getSession

functions behave in case the session is expired? Do they check this? or will they return `null`/`undefined` in such an scenario?

Colleagues, I need some advice. Can I use Google OAuth Access Token to authorize my server? How do I validate them?

Hey guys I'm using next js, getting infinite call

/refresh

on Safari (Works fine from Chrome) ``` SuperTokens.init({ appInfo: { appName: 'Test', apiDomain: 'http://localhost:3000', websiteDomain: 'http://localhost:8080', apiBasePath: '/api/v1/public/auth', websiteBasePath: '/auth' }, recipeList: [ Passwordless.init({ contactMethod: 'EMAIL' }), Session.init({ cookieDomain: 'http://localhost:8080' }) ] })

For some reason I can't call

/auth/signout

. Getting unauthorized errors. How exactly does that happen? 🤔

I am testing a service using a hosted production supertokens using a valid sms key, and I need to perform OTP sign in many times. However all of a sudden I stopped receiving sms messages and there are no logs in the console. I am wondering if this could be due to some default spam detection or if this could be due to some rate limiting against my phone number?

hey @josephmilanmd our sdk does not return a 403 for this route. Maybe something else is doing that on your end?

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 Supertokens Team, I hope this message finds you well. I am currently working on integrating Supertokens into my application, which consists of Vue.js on the frontend and Nest.js on the backend. Initially, I successfully implemented the Supertokens login functionality using the SaaS version, and everything worked smoothly. To facilitate local development, I decided to switch to the Docker version of Supertokens by setting up a local instance and updating the connectionUrl accordingly. After successfully completing the setup, including table creation, both the Supertokens core and database containers appear to be running correctly on my local environment. However, upon switching the backend's connectionUri to the local URL, I encountered an issue. The login form displays as expected, and I can successfully log in with Google authentication. However, instead of being redirected to the application's homepage, the Supertokens session refresh logs continuously appear, causing an infinite loop. When I revert the connectionUri to the SaaS version, everything functions correctly. I've attached a portion of the logs generated endlessly on the frontend for your reference. Could you please provide guidance on what might be causing this issue? Any insights or suggestions would be greatly appreciated.