Hey guys, awesome project, love it I 've been debugging this for a few hours. What could be the reason that I don't have

sRefreshToken

cookie. What would be useful information I can provide?

Hey, i'm getting errors with Facebook login, it worked for me while the app was in development mode on facebook developers, but after moving my app to 'live' on Facebook i'm getting a 400 (corrected from 404) i'm using nest + graphql + react

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;
  }
}

Meant to pop in earlier. 😅 Hope that was a fun time.

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?

Hey team , I am using managed solution for supertoken and I received "No SuperTokens core available to query". I received this error around 12:54. Was supertoken down during that period . As currently I am not receiving that error and auth is working fine .

When I'm selfhosting, I'm still limited by the paid features ? Like, max 3 dashboard users ?

Hello! I'm following https://supertokens.com/docs/emailpassword/custom-ui/init/backend with a fastAPI+Postgres. Should the

/auth

routes be visible in the OpenAPI

/docs

endpoint if I did everything according to the link above? TIA for any help!

Is anyone here who implements supertokens with express backend with custom nextjs UI?

hey i am using thirdpartypasswordless and the user can signin using there phone or email and as per requirement we want to get the user input values in frontend state so please tell how can we get this?