Hi, i try to use supertokens on nuxtjs with nuxt-auth. i have write a custom scheme extends cookies scheme. The question is, can i use "sIRTFrontend" to determine whether the session is alive on the middleware checking?

Hi there, these are the cookies I have in the browser when I'm (supposed to be) signed in. https://prnt.sc/0-c7XPkIYqoh Is this correct? If yes, then why do I get this response on auth/me? https://prnt.sc/s29fUDnToVcg

unauthorised issue

How do we use supertokens with our own UI when also using SSR?

Hi everyone, I was wondering something about the 3rd party + email recipe. let's say someone uses google signin and then tries to signup using the same email address. I notice that in the database there are 2 users created with the same email (and different userids ofcourse) is it possible to configure supertokens to prevent that? I would like to use the email as user id and when the user tries to signup with the same gmail address to get an error about they are being already registered

Hey! Is it possible to check if the user already has a session inside

thirdPartySignInUpPOST

override? I tried something like

await verifySession({ sessionRequired: false })(input.options.req, input.options.res);

but that errors out.

Session existence in sign up API

Does GetProfileInfo return the account from the provider? Like am I able to point GetProfileInfo at an api endpoint to retrieve things like the provider ID, avatar, etc.

Hi, I'm trying to implement supertokens into my nestjs + nextjs application with ThirdPartyEmailPassword. I encountered an error when trying to signin/signup with Google. The account is successfully signup/signin in the development environment but the /signinup api failed with status code 500 on frontend 400 on backend, then the error got displayed on the form. When reload the frontend application, it does recognize that I've logged in and redirect to the home page tho.

In the signinuppost function I'm overriding it and doing an API call with the user's access token to get their discord user data. This works, but I'm wondering how I pass this info to the session. I have overriden the session function as well, so do I just pass this variable through the usercontext?

Is there any chance a function could be added that returns the session found on the server instead of (or in addition to) adding it to the

request

object? (Talking about

Node.js

here.) I'm playing around with

Svelte Kit

. And it seems like they don't give us access to any data tacked onto the request object. I'm trying to figure out if there's a more functional way to get the session instead. 🤔

Alternative way to get session

any one successfully deployed the helm chart with argo cd?

hello - I run offscript.io - we have a problem where our users don't get the setup a new password whne the users request so

we'd need your help to solve this

hey, I ditched nextjs and followed the nestJS docs. now im running into this error

Error: Cannot find module 'faunadb'

. But i cant find anything related to

faunadb

in the docs

Hey, usually the signOut flow just simply worked. I called two supertokens function at the frontend side (Next.js)

typescript
await EmailPasswordReact.signOut();
await EmailPasswordReact.redirectToAuth({ show: "signin" });

And it cleared all my cookies and redirected to the login page. It was pretty much it, but i noticed, that after i added a change password functionality to my site and after i successfully changed my password the EmailPasswordReact.signOut function call didn't cleared my cookies. I had to delete them manually then after a relogging, it worked just as before. I checked my backend(Nest.js) code and it seems fine

typescript
  @Post("/change-password")
  @UseGuards(AuthGuard)
  async changePassword(
    @Session() session: SessionContainer,
    @Body() changePasswordDto: ChangePasswordDto,
    @Res() res: Response
  ) {
    const { currentPassword, newPassword } = changePasswordDto;

    const userId = session.getUserId();
    const userInfo = await EmailPasswordNode.getUserById(userId);

    if (userInfo === undefined) {
      throw new Error("Should never come here");
    }

    const isPasswordValid = await EmailPasswordNode.signIn(userInfo.email, currentPassword);

    if (isPasswordValid.status !== "OK") {
      throw new BadRequestException("Hibás jelenlegi jelszó");
    }

    const response = await EmailPasswordNode.updateEmailOrPassword({
      userId,
      password: newPassword
    }).catch((error) => {
      console.log(error);
      throw new InternalServerErrorException("Váratlan hiba");
    });

    if (response.status !== "OK") {
      throw new InternalServerErrorException("Váratlan hiba");
    }

    await SupertokensSession.revokeAllSessionsForUser(userId);
    await session.revokeSession();

    return res.status(401);
  }

Do you guys have any idea what i did wrong ? Thanks for the answers in advance 🙂

Sign out issue

I followed the steps in this docs https://supertokens.com/docs/emailpassword/nextjs/init but I'm getting an infinite redirect

the url is like this in the infinite redirects http://localhost:3000/auth?rid=emailpassword&redirectToPath=%2Fauth

I am implementing the passwordless authentication using supertokerns. So, for backend, from the example given on github, I have to add api-server/index.js file and mailer.js file? or only implement index.js file? and supertoken will send mail to users?

is

SuperTokens.init

from

import SuperTokens from 'supertokens-website';

a singelton? I want to use

SuperTokens.doesSessionExist()

in an auth guard. The

init

is in another service. with angualr

It is a singleton

okey, there is something i don't get 🙈 I have passwordless with nestjs in the backend. I got Cookies back. I expect, if i call

SuperTokens.doesSessionExist()

directly after the response, I should have a valid Session. thats not the case. Do I miss a step?

Do we have graphql endpints for login/signup requests?

Does SuperTokens provide away for backends to communicate like Auth0? Or is it only for frontends communicating with backends?

Backed communication

Hello there, my dev team has been able to add supertokens auth (passwordless magic link + social) to a react webclient, as documented by supertokens. Now, the same login system should be used in the mobile application, do you support a way to handle this with the magic link? Right now if our react native app would POST /code, the user clicking the link would be redirected on the web. What should be done?

[passwordless] I'm having this issue where the authentication does not work on mobiles, but it does work on desktops, any ideas on what it could be about? It's the same web app, same everything

Mobile app support