Hi Guys, We got 1 hasura instance and 1 supertoken instance but 2 apps with 2 endpoints

/api/auth

. We have to provide a JWKS endpoint. Is it oké to provide just 1 endpoint?

Anyone, by chance, have implemented supertokens with capacitor? We're struggling to get it working

(tagged you in a thread related to capacitor integration)

hey@

Can I wrap my whole React app in

<ThirdPartyEmailPasswordAuth> ... </ThirdPartyEmailPasswordAuth>

while still requiring auth in some place and not others?

Is there a way to add some additonal params into the passwordless signiniup endpoint and then include those in the magic link url that gets sent back to the user?

I did implement it, with using the server.url option tho, so the app is basically a webview that fetches my app from a live url

It works well with android, did not try iOS yet

I just needed the capacitor to be able to use the Push Notifications

You can go down the same route if you dont plan on supporting offline use for the app

And being able to push/deploy live updates without requiring users to update the app is also a cool sideeffect

ah thanks, we already got our app in production for a whole for iOS / android so can't change the server url 😦

invalid_grant with override on thirdparty

Hey, I just launched the core part in a docker container with docker-compose and I am wondering if there is a way to reduce the amount of logging to console? I have found this link that redirected me here: https://supertokens.com/docs/passwordless/common-customizations/core/logging

Hi, when I initialise supertokens on the server side, I always pass an appName as well. Is it possible to have a core instance of supertokens that distinguishes users by appName? So that, for example, 2 projects exist and 1 supertokens core. The two projects both initialise supertokens in the BackEnd with 2 different app names. If the user with the email foo@bar.de logs in to project 1, he is not automatically logged in to project 2. Is this possible? Thank you for your work

Hi, when I login using supertokems in my nextjs web app, it is being redirected to path '/'. I want to chelange this path. What to do?

I need to redirect to '/hello' on successfull login

Redirecting path change

Is there a limit to how much a person can test resetting passwords for emails? I'm trying to do resets but they don't seem to be popping up in my email. (They worked previously.)

Hi! What's the recommended way to migrate users to Supertokens? They're just in a DB table, not another identity service. Should I just insert them into the [recipe]_users table? And metadata into the metadata table

Migration to supertokens

Is there an API endpoint to change a user's password when they're already logged in?

Is there an API endpoint to change a

https://www.ory.sh/oauth2-openid-connect-do-you-need-use-cases-examples/ Hello folks, I wanted to get the team's opinion on a criticism of supertokens in the above article. I am putting a screenshot of the relevant section for reference

OAuth 2.0 confusion

async function doesSessionExist() {
    if (await SuperTokens.doesSessionExist()) {
      // user is logged in
      console.log("there is a session");
    } else {
      // user has not logged in yet
    }
  }

this returns error in react native

The SuperTokens backend APIs are supposed to let us know if the response didn't turn out okay, right? Will it let us know through the

response.status

? Or do we have to find out from the

response.json().status

? (Stated differently, is there a way to know that an error occurred without JSON-ing the response?)

Hi everyone, I'm new to Super Tokens and what's wondering if there are any docs/examples/pointers on how to - create users and set a temporary password that they are prompted to change after first login - allow admin to reset a user's password or to suspend a user TIA

question about

context.redirectPath

-> can the url be "dynamic" based on some condition?

I have this

EmailPasswordReact.init({
        getRedirectionURL: async (context) => {
          if (context.action === "SUCCESS") {
            if (context.redirectToPath !== undefined) {
              // navigate back to where the user was before authenticated
              return context.redirectToPath;
            }
            return "/dashboard";
          }
          return undefined;
        },