hello.@rp_st when resetting password, how can I detect if newPassword is the same as old one? supertokens server is selfhosted, and is seperated from api backend. the only receives when resetting password are just password and token.

I want to override the SessionAuth's behaviour of checking if the session is present or not and if not redirect to login page. I know I need to modify the overrideGlobalClaimValidators field but I am having troubles finding documentation on it. I don't know what exactly to put. All I know is the authorization part where it checks the roles.

Hey @rp_st , need ur help in social logins at backend this is my config for google

config: {
          thirdPartyId: THIRD_PARTY.GOOGLE,
          clients: [
            {
              clientId: process.env.GOOGLE_CLIENT_ID,
              clientSecret: process.env.GOOGLE_CLIENT_SECRET,
              clientType: CLIENT_TYPE.WEB,
            },
            {
              clientId: process.env.IOS_GOOGLE_CLIENT_ID,
              clientType: CLIENT_TYPE.IOS,
            },
            {
              clientId: process.env.ANDROID_GOOGLE_CLIENT_ID,
              clientType: CLIENT_TYPE.ANDROID,
            },
          ],
        },

from frontend i am calling the api

curl -X 'POST' \
  'http://localhost:3001/auth/signinup' \
  -H 'accept: application/json' \
  -H 'rid: thirdpartypasswordless' \
  -H 'Content-Type: application/json' \
  -d '{
  "thirdPartyId": "google",
  "clientType": "ios",
  "redirectURIInfo": {
    "redirectURIOnProviderDashboard": "",
    "redirectURIQueryParams": {
      "code": "4/0AeaYSHB4c8QnHY7fjQS0K8j169tLw6ONPV-5-JB7HfQ6tsa6Jq0GHyu0VDAz53L5LdYUZQ"
    }
  }
}'

but always getting error such as

Error: Received response with status 400 and body {
  "error": "invalid_grant",
  "error_description": "Bad Request"
}
    at Object.exchangeAuthCodeForOAuthTokens (C:\Users\Ankit Gupta\Desktop\dh\dh-prajavani-auth\api\node_modules\supertokens-node\lib\build\recipe\thirdparty\providers\custom.js:259:23)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.signInUpPOST (C:\Users\Ankit Gupta\Desktop\dh\dh-prajavani-auth\api\node_modules\supertokens-node\lib\build\recipe\thirdparty\api\implementation.js:26:36)

please help me out

Hi, I have nodejs app with react. On the deployement domain, the application works perfect. Also, on the localhost it works perfect. But, I have a react developer that only has the react app. The app is pointing to the deployment server because I cant install the entire app at his computer. This way he can develop client side features without the server complexity. The problem is that the react is at

localhost:9001

the remote server is at

domain.com

. he is able to login, and immedietly after the redirection to the success page he gets disconnected. I assume It is because we operating the app under 2 domains

localhost:9001

and

domain.com

. how can I configure the app info on the client side to supprt that? is that possible to have 2 different domains? Thanks

Hi I'm trying to use custom form fields in Angular/Node.js.. I keep getting: "Are you sending too many / too few formFields?" I have the form fields setup on backend but frontend with Angular not really working

Is it possible to modify the "Sign In" text in the prebuilt UI such as adding additional text?

I am just starting to work with supertokens. I prepared the project as in the tutorial for AWS lambda. I stopped at the 404 problem and prepared the frontend on this init: appInfo: { appName: "SuperTokens Demo App", apiDomain: "https://api.example.com", apiBasePath: "/auth", apiGatewayPath: "/", websiteDomain: "https://frontend.example.com", }, I prebuild UI and i works. When I try type email to sign up I see network issue: Request URL: https://api.example.com/auth/signup/email/exists?email=asda%40dsa.com Request Method: GET Status Code: 404 Not Found But when I opened this page I see response: {"status":"OK","exists":false} CORS works: Request URL: https://api.example.com/auth/signup/email/exists?email=asda%40dsa.com Request Method: OPTIONS Status Code: 200 OK I use the API GW V2 with integration for route: ANY /auth/{PROXY+}

I am trying to set debug: true in init, however typeInut doesn't have definition of debug. using supertokens-node 14.0.2

You may be familiar of the server actions in nextjs. How do I protect the server actions for authorized usage ? We can protect the api with "withSession" helper function but as we dont have any request in server actions so I can use that func.

Hey, after updating to version 7 of supertokens core and version 16 of supertokens-node, I'm facing following error during user signup.

Error: UNKNOWN_USER_ID
    at EmailVerificationClaimClass.fetchValue (/Users/f//backend/node_modules/supertokens-node/lib/build/recipe/emailverification/emailVerificationClaim.js:31:27)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at EmailVerificationClaimClass.build (/Users/f/backend/node_modules/supertokens-node/lib/build/recipe/session/types.js:9:23)
    at Object.createNewSessionInRequest (/Users/f/backend/node_modules/supertokens-node/lib/build/recipe/session/sessionRequestFunctions.js:351:24)
    at Function.createNewSession (/Users/f/backend/node_modules/supertokens-node/lib/build/recipe/session/index.js:48:16)
    at Object.signUpPOST /Users/f/backend/node_modules/supertokens-node/lib/build/recipe/emailpassword/api/implementation.js:561:27)
    at Object.emailPasswordSignUpPOST (/Users/f/backend/apps/supertokens-service/src/supertokens/services/recipes/third-party-email-password.overrides.ts:561:22)...

Not sure it this could be the cause, but at the end of emailPasswordSignUp we call

const response = await originalImplementation.emailPasswordSignUp(
          input,
        );

    /* code for fetching external user */

    await createUserIdMapping({
          superTokensUserId: response.user.id,
          externalUserId: external.user.id,
        });

    response.user.id = external.user.id;
    return response;

We are using: image: registry.supertokens.io/supertokens/supertokens-postgresql:7.0