Hey, got a question regarding axios interceptors. Since we no longer need to explicitly set interceptors, how can I choose which axios instance the supertokens chould use? (is that possible) (using vue3 and go)

Hey, I have a website and a chrome extension. What i want to do is when the user logins inside the website, he should automatically login inside the extension as well. This is a business project.

Hello, wanted to say that I'm struggling a little running the user roles recipe on Safari (works on Chrome) due to line 47 of logger.js: "return errorStack[i].match(/(?<=\().+?(?=\))/g);". This kind of regular expression is not supported in Safari and gives a "SyntaxError: Invalid regular expression: invalid group specifier name". Are there any fixes for this so that I could run my webite on Safari? Edit: logger.js is at supertokens-node/lib/build/logger.js

I'm having trouble with NestJS + GraphQL, I've seen there were older messages about this in discord but it didn't really help... Honestly I have no clue of how, according to the supertokens documentation of vanilla graphql on nodejs, this should be done:

ts
@Injectable()
export class GQLAuthGuard implements CanActivate {
  async canActivate(context: ExecutionContext): Promise<boolean> {
    const ctx = GqlExecutionContext.create(context).getContext();

    let err = undefined;
    // You can create an optional version of this by passing {sessionRequired: false} to verifySession
    await verifySession({ sessionRequired: false })(
      ctx.req,
      ctx.res,
      (res) => {
        err = res;
      },
    );

    if (ctx.res.headersSent) {
      throw new STError({
        message: 'RESPONSE_SENT',
        type: 'RESPONSE_SENT',
      });
    }

    if (err) {
      throw err;
    }

    return true;
  }
}

Hey there, is there a way to autostart supertokens on ubuntu? After restart it's not automatic

Hi, I'm facing a problem with the

st-auth-mode

request header. First, I do a signup request (using the email password recipe) where I set the header

st-auth-mode: cookie

. I then get a response with

Set-Cookie

headers for the access token and refresh token. This is as expected. Next, I do a signup request where I don't set the

st-auth-mode

header. I then get a response with both

Set-Cookie

headers and

st-access-token

and

st-refresh-token

headers. I do not expect to get the

Set-Cookie

headers. I do a signup request one more time, again without setting the

st-auth-mode

header. This time only the

st-access-token

and

st-refresh-token

headers are set. This is as expected. All signup requests I do afterwards without the

st-access-token

header give the same proper result. The second request should not have returned the

Set-Cookie

headers. Is this a known issue or am I doing something wrong?

Hi, I would like to use nock to mock the API call behaind

thirdPartySignInUpPOST

because of some account linking logic we do after it that I would like to test. can you help me understand how the request path looks like and what should be an example of the response? I'm going to use nock to do that if it makes any difference for you

Hi, is there a way to mount the dashboard endpoint to a separate port with a seperate domain and gateway settings? except the obvious way of creating a separate deployment of our BE service for that purpose?

Implementing a refresh token flow as explained in https://supertokens.com/docs/session/common-customizations/sessions/ssr#3-implementing-the-refresh-session-flow-refresh-session-pagr causes the whole web app to 'flash' every time a token is refreshed, because we navigate to the /refresh-session page (using Remix in my example). Is there a way to refresh the token on the server during the request instead of redirecting to a front-end page that needs to do an API call and redirect back?

Hey @rp_st for older version of supertoken node - 12.x.x , do we have multitenancy as the recipe ? const Multitenancy = require("supertokens-node/recipe/multitenancy"); I couldn't find this file. Its throwing an error.